Triple
T20387619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prime Timeline |
E497997
|
entity |
| Predicate | hasStartEra |
P39608
|
FINISHED |
| Object | mid-22nd century (Star Trek: Enterprise era) |
—
|
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: mid-22nd century (Star Trek: Enterprise era) | Statement: [Prime Timeline, hasStartEra, mid-22nd century (Star Trek: Enterprise era)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStartEra Context triple: [Prime Timeline, hasStartEra, mid-22nd century (Star Trek: Enterprise era)]
-
A.
hasPrimaryEra
Indicates that an entity is chiefly associated with or belongs to a particular historical or temporal era.
-
B.
hasEraReset
Indicates that a new era or time period has been initiated, resetting the previous temporal sequence or counting.
-
C.
precedesEra
Indicates that one time period or era occurs entirely before another in chronological order.
-
D.
singleMatchEraStart
Indicates the point in time when a particular single-match era or period begins.
-
E.
notableEraStart
chosen
Indicates the point in time when a notable or historically significant era associated with an entity begins.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6790c935881908f901d058e6a83a9 |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:28 a.m.