Triple
T26853572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telmarines |
E676120
|
entity |
| Predicate | timePeriodInNarnia |
P11197
|
FINISHED |
| Object | ruled Narnia for several hundred years |
—
|
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: ruled Narnia for several hundred years | Statement: [Telmarines, timePeriodInNarnia, ruled Narnia for several hundred years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodInNarnia Context triple: [Telmarines, timePeriodInNarnia, ruled Narnia for several hundred years]
-
A.
timeInMyth
Indicates that an entity exists or occurs during a specific time period within a mythological narrative or tradition.
-
B.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
C.
timeOfNarrative
chosen
Indicates the specific time or period during which the events of a narrative are set or unfold.
-
D.
timePeriodFormulated
Indicates the time period during which something (such as a concept, theory, or plan) was formulated or developed.
-
E.
narrativeTimeSpanHours
Indicates the duration of a narrative or story event measured in hours.
- 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_69eee9b9d7708190a15d7485709ae981 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 5:19 a.m.