Triple
T30570450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta Quadrant |
E778107
|
entity |
| Predicate | primaryExplorationVessel |
P35089
|
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, primaryExplorationVessel, USS Voyager]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryExplorationVessel Context triple: [Delta Quadrant, primaryExplorationVessel, USS Voyager]
-
A.
expeditionShip
chosen
Indicates a relationship where a ship is designated or used specifically for conducting an expedition or exploratory mission.
-
B.
researchVessel
Indicates that an entity is a vessel specifically used for conducting research or scientific investigation.
-
C.
vesselTypeServedOn
Indicates the type of vessel on which an entity has served or performed duty.
-
D.
namedVesselOf
Indicates that one entity is the specific named vessel (e.g., ship, boat, or craft) associated with or belonging to another entity.
-
E.
discoveryExpedition
Indicates an expedition undertaken with the purpose of exploring or discovering new places, phenomena, or information.
- 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_6a03008316dc8190a9f6faf48d25a4f8 |
completed | May 12, 2026, 10:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2863ccb1348190a5d7ddf4e1cf3e0a |
completed | June 9, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_6a030023e66881909ea79f1365ab538a |
completed | May 12, 2026, 10:25 a.m. |
Created at: April 29, 2026, 8:22 p.m.