Triple
T9998347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USCSS Prometheus |
E197260
|
entity |
| Predicate | launchYearInFiction |
P16819
|
FINISHED |
| Object | 2089 |
—
|
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: 2089 | Statement: [USCSS Prometheus, launchYearInFiction, 2089]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchYearInFiction Context triple: [USCSS Prometheus, launchYearInFiction, 2089]
-
A.
foundedInFictionalYear
chosen
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.
-
B.
firstPublicationYearOfAppearance
Indicates the year in which an entity (such as a work or character) first appeared in a published form.
-
C.
fictionalUniverseDebut
Indicates the first appearance of an entity within a particular fictional universe or continuity.
-
D.
firstPublishedInAtlasInYear
Indicates the year in which an entity was first published or appeared in a specific atlas.
-
E.
landingYear
Indicates the year in which a landing event (such as an arrival or touchdown) took place.
- 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_69ca82f3b61c81908ecc2c1c96dbc2e4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdcc8c78448190a5332f4ff8a7b3dd |
completed | April 2, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69cd1da07db88190945bcdab3ca82e71 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:51 p.m.