Triple
T37512788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eternal Conflict |
E932556
|
entity |
| Predicate | inUniverseTimespan |
P179948
|
FINISHED |
| Object | eternal |
—
|
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: eternal | Statement: [Eternal Conflict, inUniverseTimespan, eternal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseTimespan Context triple: [Eternal Conflict, inUniverseTimespan, eternal]
-
A.
inUniversePeriod
chosen
Indicates that something exists, occurs, or is valid within a specified time period in a particular fictional or conceptual universe.
-
B.
inUniverseLength
Indicates that one entity specifies or measures the length of another entity within a particular universe or contextual framework.
-
C.
inUniverseDate
Indicates that an entity is associated with or occurs on a specific date within a fictional or defined universe’s internal timeline.
-
D.
inUniverseAge
Indicates the age of an entity as measured within the timeline or continuity of a specific fictional or defined universe.
-
E.
timeInUniverseEnds
Indicates that the duration or existence of the universe comes to a final end at a specified time or event.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: May 3, 2026, 4:17 p.m.