Triple
T27421046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naʽakuto Laʽab |
E693043
|
entity |
| Predicate | traditionalSuccessorOf |
P60459
|
FINISHED |
| Object | Lalibela |
—
|
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: Lalibela | Statement: [Naʽakuto Laʽab, traditionalSuccessorOf, Lalibela]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalSuccessorOf Context triple: [Naʽakuto Laʽab, traditionalSuccessorOf, Lalibela]
-
A.
successorInPractice
Indicates that one entity has taken over the role, position, or function of another in actual practice, even if not formally or officially designated as its successor.
-
B.
successorDeterminedBy
Indicates that the identity of a successor is established or chosen according to a specified rule, process, or determining factor.
-
C.
successorType
chosen
Indicates the specific kind or category of successor relationship that holds between one entity and the next in a sequence or hierarchy.
-
D.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
-
E.
successorUse
Indicates that one entity is used or applied as the subsequent or follow-up use of another entity in a sequence or lifecycle.
- 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_69ef5208617081908f731d312e0fd1bc |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 27, 2026, 12:36 p.m.