Triple
T34834450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louis, Duke of Guyenne |
E1004159
|
entity |
| Predicate | monarchServedAsHeirTo |
P56799
|
FINISHED |
| Object | Charles VI of France |
—
|
NE NERFINISHED |
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: Charles VI of France | Statement: [Louis, Duke of Guyenne, monarchServedAsHeirTo, Charles VI of France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monarchServedAsHeirTo Context triple: [Louis, Duke of Guyenne, monarchServedAsHeirTo, Charles VI of France]
-
A.
monarchSheIsHeirTo
chosen
Indicates that the subject is the designated heir to the specified monarch’s throne or title.
-
B.
monarchSuccessor
Indicates that one monarch directly follows another in a royal line of succession.
-
C.
succeededOnThroneAfter
Indicates that one entity became the ruler or monarch immediately following another entity’s reign on the same throne.
-
D.
succeededToThroneBy
Indicates that one ruler or monarch is followed in succession by another who takes over the throne.
-
E.
hereditaryMonarch
Indicates that a person holds a monarchical position that is passed down through a family line according to hereditary succession rules.
- 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_69f76db7d1b4819093bd4912d80d845d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.