Triple
T36550360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buckland Gate |
E901241
|
entity |
| Predicate | timePeriodWithinLegendarium |
P174087
|
FINISHED |
| Object | late Third Age |
—
|
LITERAL FINISHED |
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: late Third Age | Statement: [Buckland Gate, timePeriodWithinLegendarium, late Third Age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodWithinLegendarium Context triple: [Buckland Gate, timePeriodWithinLegendarium, late Third Age]
-
A.
legendaryPeriod
Indicates a time span associated with legends or mythic events rather than strictly historical chronology.
-
B.
timeInMyth
Indicates that an entity exists or occurs during a specific time period within a mythological narrative or tradition.
-
C.
dateInLegendarium
chosen
Indicates that a given date occurs within the fictional historical timeline (legendarium) of a particular narrative world.
-
D.
timePeriodOfLegend
Indicates the time period during which a particular legend is traditionally set or believed to have occurred.
-
E.
timePeriodOfFameInUniverse
Indicates the span of time within a fictional or defined universe during which an entity is considered famous or widely recognized.
- 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_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: May 3, 2026, 4:11 p.m.