Triple
T29654769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daelaam |
E750235
|
entity |
| Predicate | temporarySeatOfPower |
P38122
|
FINISHED |
| Object | Shakuras |
—
|
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: Shakuras | Statement: [Daelaam, temporarySeatOfPower, Shakuras]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporarySeatOfPower Context triple: [Daelaam, temporarySeatOfPower, Shakuras]
-
A.
temporaryChair
Indicates that an entity serves as a chair or leader of a group or organization for a limited, non-permanent period.
-
B.
ruledInPlaceOf
Indicates that one entity exercised governing authority or leadership as a substitute or proxy for another entity.
-
C.
usedAsSeatOfPowerBy
chosen
Indicates that something serves as the primary location or base from which an individual or group exercises authority, control, or governance.
-
D.
seatOfPowerType
Indicates the type or category of a seat of power associated with an entity (e.g., political, religious, administrative).
-
E.
laterSeatOfGovernment
Indicates that the referenced place served as a subsequent seat of government for the same political entity after an earlier one.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 6:54 p.m.