Triple
T6954638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Orville (ECV-197) |
E161210
|
entity |
| Predicate | designerInUniverse |
P184
|
FINISHED |
| Object | Planetary Union engineers |
—
|
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: Planetary Union engineers | Statement: [USS Orville (ECV-197), designerInUniverse, Planetary Union engineers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designerInUniverse Context triple: [USS Orville (ECV-197), designerInUniverse, Planetary Union engineers]
-
A.
createdInUniverseBy
Indicates that something was brought into existence within a particular fictional or conceptual universe by a specific creator or originating agent.
-
B.
designedBy
chosen
Indicates that one entity is the creator, planner, or architect responsible for the form or structure of another entity.
-
C.
designerOccupation
Indicates that one entity serves as the professional designer or design specialist for another entity.
-
D.
creativeUniverse
Indicates a relationship where an entity is responsible for originating, shaping, or imaginatively generating a universe or complete world.
-
E.
designerNationality
Indicates that a designer has a specific national or country affiliation.
- 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_69c68852a9a0819097797e31d492e273 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dace1a94819095311e4288f01784 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bf0a7c8190b5ed4aca22ba9b97 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:29 p.m.