Triple
T26325922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lan Xang |
E662250
|
entity |
| Predicate | brokeUpDueTo |
P35030
|
FINISHED |
| Object | succession disputes |
—
|
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: succession disputes | Statement: [Lan Xang, brokeUpDueTo, succession disputes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brokeUpDueTo Context triple: [Lan Xang, brokeUpDueTo, succession disputes]
-
A.
brokeUpIn
Indicates that a romantic or close relationship between entities ended in a specified location or context.
-
B.
breaksUpWith
Indicates that one entity ends a romantic or intimate relationship with another entity.
-
C.
breakup
Indicates the ending or dissolution of a romantic or close personal relationship between two entities.
-
D.
breakupLinkedTo
chosen
Indicates a causal or associative relationship where a breakup is connected to, influenced by, or results from another event, factor, or entity.
-
E.
breakupDate
Indicates the date on which a romantic or partnership relationship between two entities ended.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 10:31 p.m.