Triple
T23905180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T'Lar |
E601171
|
entity |
| Predicate | universeTimeline |
P105551
|
FINISHED |
| Object | Prime Timeline |
—
|
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: Prime Timeline | Statement: [T'Lar, universeTimeline, Prime Timeline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: universeTimeline Context triple: [T'Lar, universeTimeline, Prime Timeline]
-
A.
inUniverseHistory
chosen
Indicates that an event, fact, or narrative element occurs within the fictional universe’s own internal timeline or recorded history, rather than in real-world or out-of-universe context.
-
B.
cosmologicalPeriod
Indicates a temporal relationship where something occurs, exists, or is defined within a specific cosmological era or phase of the universe.
-
C.
eraChronology
Indicates the temporal ordering relationship that places an era within a specific position in a broader historical or chronological sequence.
-
D.
viewOnAgeOfUniverse
Indicates a stance or belief an entity holds regarding the age of the universe.
-
E.
chronologyOf
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with another entity.
- 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cde13e88819086bbd0bc4a5b6a36 |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:30 p.m.