Triple
T34957662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barge of the Dead |
E1008162
|
entity |
| Predicate | starshipSetting |
P182129
|
FINISHED |
| Object | USS Voyager |
—
|
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 Voyager | Statement: [Barge of the Dead, starshipSetting, USS Voyager]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: starshipSetting Context triple: [Barge of the Dead, starshipSetting, USS Voyager]
-
A.
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.
-
B.
starshipRegistry
Indicates a formal registration relationship where a starship is recorded in an official registry or database.
-
C.
starshipServedOn
Indicates that a person was assigned to and served aboard a particular starship.
-
D.
hasStarship
Indicates that one entity possesses, controls, or is associated with a particular starship.
-
E.
spaceStationConfiguration
Indicates the specific structural and functional arrangement of modules, systems, and components that define how a space station is organized and operates.
- F. None of above. chosen
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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7870dfe108190996c0c68630edc7f |
completed | May 3, 2026, 5:34 p.m. |
Created at: May 3, 2026, 4 p.m.