Triple
T32686858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babylon 5: The Gathering |
E835748
|
entity |
| Predicate | introducedUniverse |
P171399
|
FINISHED |
| Object | Babylon 5 universe |
—
|
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: Babylon 5 universe | Statement: [Babylon 5: The Gathering, introducedUniverse, Babylon 5 universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedUniverse Context triple: [Babylon 5: The Gathering, introducedUniverse, Babylon 5 universe]
-
A.
introducesFictionalUniverse
chosen
Indicates that an entity is responsible for originating or first presenting a particular fictional universe or setting.
-
B.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
C.
inUniverseOrigin
Indicates that one entity originates from, or has its source within, the fictional universe or setting defined by another entity.
-
D.
inUniverseMaker
Indicates that an entity exists or occurs within the fictional universe created or defined by another entity.
-
E.
inUniverseStar
Indicates that a star exists or is located within a particular fictional or defined universe.
- 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_69f3493211388190993801216afbc2a7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: May 1, 2026, 1:09 a.m.