Triple
T25293547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Naresuan |
E634153
|
entity |
| Predicate | vassalageEnded |
P62191
|
FINISHED |
| Object | Burmese suzerainty over Ayutthaya |
—
|
LITERAL 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: Burmese suzerainty over Ayutthaya | Statement: [King Naresuan, vassalageEnded, Burmese suzerainty over Ayutthaya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vassalageEnded Context triple: [King Naresuan, vassalageEnded, Burmese suzerainty over Ayutthaya]
-
A.
vassalageEndedBy
chosen
Indicates that a prior vassal relationship between two entities has been terminated by a specific third party or event.
-
B.
vassalageEndTime
Indicates the point in time at which a vassalage relationship between two entities formally ends.
-
C.
vassalageOver
Indicates a hierarchical feudal relationship in which one party is a vassal subordinate to and owing allegiance or obligations to another.
-
D.
vassalageStart
Indicates the point in time when a vassalage relationship—where one party becomes subordinate or owes allegiance to another—officially begins.
-
E.
feudEnd
Indicates that a previously existing feud or conflict between entities has come to an end.
- F. None of above.
Provenance (3 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48fcf4bc88190a9ffaa3b07d5b881 |
completed | May 1, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:22 p.m.