Triple
T30583838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Konbaung–Hanthawaddy War |
E778450
|
entity |
| Predicate | relatedKingdom |
P20193
|
FINISHED |
| Object | Hanthawaddy Kingdom |
E280691
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Hanthawaddy Kingdom | Statement: [Konbaung–Hanthawaddy War, relatedKingdom, Hanthawaddy Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedKingdom Context triple: [Konbaung–Hanthawaddy War, relatedKingdom, Hanthawaddy Kingdom]
-
A.
kingdomAssociatedWith
chosen
Indicates a relationship where something is connected or related to a particular kingdom, such as belonging to, originating from, or being governed by that kingdom.
-
B.
kingdom
Indicates that an entity is classified within a particular biological kingdom in a taxonomic hierarchy.
-
C.
overkingdomOf
Indicates that one kingdom holds overarching authority or sovereignty over another kingdom.
-
D.
kingdomDomain
Indicates that a kingdom is part of, or belongs within, a particular higher-level domain.
-
E.
recognizedAsKingdom
Indicates that an entity is formally acknowledged or classified as a kingdom within a given system or context.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a032d9200448190a2adcc5ee48bff01 |
completed | May 12, 2026, 1:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2946fe2f388190ac1a283edecc3083 |
completed | June 10, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_6a032c9f41f08190b1c60b0afbbac01a |
completed | May 12, 2026, 1:35 p.m. |
Created at: April 29, 2026, 8:23 p.m.