Triple
T32332826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of the Alans |
E826095
|
entity |
| Predicate | successorTitles |
P8415
|
FINISHED |
| Object | King of Alania |
—
|
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: King of Alania | Statement: [King of the Alans, successorTitles, King of Alania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorTitles Context triple: [King of the Alans, successorTitles, King of Alania]
-
A.
successorTitle
chosen
Indicates the title or position that directly follows and replaces a previous one in a sequence or succession.
-
B.
successorTitlesComparedWith
Indicates that the titles of successor entities are being compared to determine their relative similarity, difference, or ordering.
-
C.
successorTitleForHolders
Indicates that one title is the official successor title that replaces or follows the titles previously held by certain holders.
-
D.
successorTitleHolders
Indicates that one entity holds a title immediately after another entity, as the successor in that title-holding sequence.
-
E.
successorTitleContext
Indicates the contextual circumstances or framework under which one title succeeds another.
- 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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: May 1, 2026, 12:47 a.m.