Triple
T29578908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French legitimism |
E753519
|
entity |
| Predicate | recognizedAsLegitimateKing |
P180718
|
FINISHED |
| Object | Louis XVIII |
—
|
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: Louis XVIII | Statement: [French legitimism, recognizedAsLegitimateKing, Louis XVIII]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedAsLegitimateKing Context triple: [French legitimism, recognizedAsLegitimateKing, Louis XVIII]
-
A.
alsoKingOf
Indicates that an entity who is king of one place is simultaneously king of another place as well.
-
B.
declaredKingWhileDavidAlive
Indicates that someone was proclaimed or assumed the role of king during a time when David was still alive.
-
C.
recognizedAsSultan
Indicates that an entity is acknowledged or accepted by others as holding the status or title of sultan.
-
D.
recognizedAsRegent
Indicates that an entity is formally acknowledged or designated as serving in the role of regent for another.
-
E.
recognizedAsSuccessorToThrone
Indicates that one entity has been formally acknowledged or designated as the heir or next in line to inherit a throne from another entity.
- F. None of above. chosen
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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
| PDg | Predicate description generation | batch_69f74c6fa6548190b03935f65429a24e |
completed | May 3, 2026, 1:23 p.m. |
Created at: April 28, 2026, 6:05 p.m.