Triple
T30570423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta Quadrant |
E778107
|
entity |
| Predicate | notableStarshipStranded |
P124624
|
FINISHED |
| Object | USS Voyager |
E1430327
|
NE 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: USS Voyager | Statement: [Delta Quadrant, notableStarshipStranded, USS Voyager]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableStarshipStranded Context triple: [Delta Quadrant, notableStarshipStranded, USS Voyager]
-
A.
occursOnStarship
Indicates that an event or action takes place aboard or within a starship.
-
B.
starshipCommanded
Indicates that one entity serves as the commanding officer or authority in charge of operating and directing the other entity, which is a starship.
-
C.
strandedIn
chosen
Indicates that an entity is left isolated or stuck in a particular place or situation without the means to leave or resolve it.
-
D.
starshipServedOn
Indicates that a person was assigned to and served aboard a particular starship.
-
E.
hasStarship
Indicates that one entity possesses, controls, or is associated with a particular starship.
- F. None of above.
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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28570057988190b6572a2268a95fe9 |
completed | June 9, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:22 p.m.