Triple
T25186699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NX-01 |
E630736
|
entity |
| Predicate | launchedInFictionalYear |
P158197
|
FINISHED |
| Object | 2151 |
—
|
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: 2151 | Statement: [NX-01, launchedInFictionalYear, 2151]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchedInFictionalYear Context triple: [NX-01, launchedInFictionalYear, 2151]
-
A.
releaseYearInFiction
Indicates the year in which a fictional work is depicted as being released or taking place within its narrative universe.
-
B.
foundedInFictionalYear
Indicates that an entity was established or created in a year that exists only within a fictional or imaginary timeline, rather than in real-world history.
-
C.
endsInFictionalYear
Indicates that an event, story, or timeline concludes in a year that exists only within a fictional or imagined setting.
-
D.
activeInFictionalYear
Indicates that an entity is active or operating during a specified fictional or imaginary year within a narrative or fictional timeline.
-
E.
fictionalBirthYear
Indicates the year in which a fictional character is stated or assumed to have been born within its narrative or canon.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 21, 2026, 12:44 p.m.