Triple
T35489973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thorin III Stonehelm |
E1025705
|
entity |
| Predicate | ruledInAge |
P183346
|
FINISHED |
| Object | Third Age |
—
|
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: Third Age | Statement: [Thorin III Stonehelm, ruledInAge, Third Age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruledInAge Context triple: [Thorin III Stonehelm, ruledInAge, Third Age]
-
A.
ruledDuringReignOf
Indicates that one entity exercised ruling authority or governance during the time period in which another entity’s reign took place.
-
B.
ruledUnderPolity
Indicates that an entity exercised rule or governance while being subordinate to, or within the authority framework of, a particular polity.
-
C.
ruledOnBy
Indicates that a decision, case, or matter has been formally decided or adjudicated by a specific authority or decision-maker.
-
D.
alsoRuled
Indicates that two or more entities shared ruling authority over the same domain or subjects, either concurrently or at different times.
-
E.
activeInReignOf
Indicates that an entity was active or operational during the time period corresponding to a specific ruler’s reign.
- 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_69f76dfbcdd881908c7b0b6bc502252b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79da8d8848190ab5ab1bdad95d58c |
completed | May 3, 2026, 7:10 p.m. |
Created at: May 3, 2026, 4:04 p.m.