Triple
T35250287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISS Enterprise |
E1018075
|
entity |
| Predicate | universeVariantOf |
P103924
|
FINISHED |
| Object | USS Enterprise (NCC-1701) |
—
|
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: USS Enterprise (NCC-1701) | Statement: [ISS Enterprise, universeVariantOf, USS Enterprise (NCC-1701)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: universeVariantOf Context triple: [ISS Enterprise, universeVariantOf, USS Enterprise (NCC-1701)]
-
A.
alternateUniverseVersionOf
chosen
Indicates that one entity is a counterpart or variant of another entity existing in a different universe or reality.
-
B.
universe
Indicates that something pertains to, exists within, or is associated with the entirety of space, time, matter, and phenomena collectively referred to as the universe.
-
C.
universeName
Indicates the name or designated title assigned to a particular universe or cosmic setting.
-
D.
inUniverseType
Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
-
E.
associatedUniverse
Indicates that one entity is linked or belongs to a particular universe, realm, or overarching world context.
- 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.