Triple
T36549952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shire Reckoning |
E901232
|
entity |
| Predicate | yearZeroName |
P6439
|
FINISHED |
| Object | Year of the Shire |
—
|
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: Year of the Shire | Statement: [Shire Reckoning, yearZeroName, Year of the Shire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearZeroName Context triple: [Shire Reckoning, yearZeroName, Year of the Shire]
-
A.
yearZero
chosen
Indicates that the referenced year is designated as the starting point (year 0) of a particular calendar, timeline, or counting system.
-
B.
newYearName
Indicates that an entity has a specific name or designation used for or during the New Year.
-
C.
yearTitleCreated
Indicates the year in which the referenced title (such as a work, document, or creative piece) was originally created.
-
D.
eraYearOne
Indicates that the referenced year is designated as the first year of a particular era or calendrical system.
-
E.
eraStartYearBC
Indicates the year (counting backward from year 1) in which a particular era or period begins, expressed in the BC (Before Christ/BCE) dating system.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.