Triple
T25186663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enterprise NX-01 |
E630735
|
entity |
| Predicate | keyStoryArc |
P83049
|
FINISHED |
| Object | Xindi crisis |
—
|
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: Xindi crisis | Statement: [Enterprise NX-01, keyStoryArc, Xindi crisis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyStoryArc Context triple: [Enterprise NX-01, keyStoryArc, Xindi crisis]
-
A.
notableStoryArc
Indicates that there exists a significant or prominent narrative storyline or plot development involving the subject.
-
B.
coreNarrative
chosen
Indicates the primary storyline or central sequence of events that forms the main thread of a narrative.
-
C.
storyline
Indicates that one entity serves as the narrative plot or sequence of events associated with another entity.
-
D.
storyArcLength
Indicates the duration or extent of a narrative arc within a story, such as how long a particular plotline continues.
-
E.
firstMajorStoryArc
Indicates that the related entity represents the initial or earliest major story arc associated with another narrative work or series.
- 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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46e0aeb588190b3ee13a6c031c223 |
completed | May 1, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 12:44 p.m.