Triple
T34762775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunland |
E1002110
|
entity |
| Predicate | chronologyEra |
P36399
|
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: [Dunland, chronologyEra, Third Age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologyEra Context triple: [Dunland, chronologyEra, Third Age]
-
A.
representsEra
chosen
Indicates that one entity designates the historical era, period, or age to which another entity belongs or is associated.
-
B.
eraChronology
Indicates the temporal ordering relationship that places an era within a specific position in a broader historical or chronological sequence.
-
C.
chronologyType
Indicates the type or system of chronological ordering or dating applied to an event, period, or sequence.
-
D.
recurringEra
Indicates a relationship where a particular era or time period repeats or recurs, rather than occurring only once.
-
E.
positionInEra
Indicates the temporal placement or role of something within a specific historical or chronological era.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
Created at: May 3, 2026, 3:59 p.m.