Triple
T35051303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Era of Tamriel |
E1011335
|
entity |
| Predicate | startRuler |
P182050
|
FINISHED |
| Object | Tiber Septim |
—
|
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: Tiber Septim | Statement: [Third Era of Tamriel, startRuler, Tiber Septim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startRuler Context triple: [Third Era of Tamriel, startRuler, Tiber Septim]
-
A.
newRuler
Indicates that an entity has newly assumed a position of rulership or authority over another entity or domain.
-
B.
beganWithRuler
chosen
Indicates that an event, period, or sequence started under the authority or reign of a specified ruler.
-
C.
recognizedAsRuler
Indicates that one entity is acknowledged or accepted by others as the legitimate ruler or sovereign authority.
-
D.
rulerDuringConstruction
Indicates that a particular person held ruling authority over a place or polity during the time a specific construction project was carried out.
-
E.
involvesRuler
Indicates that the relationship or action includes or pertains to a ruler as a participating party.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00532815c881908f10d9594458b3d7 |
completed | May 10, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_6a0052b9f030819081b8105bdcaf6d8f |
completed | May 10, 2026, 9:41 a.m. |
Created at: May 3, 2026, 4:01 p.m.