Triple
T34969441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homestead (Star Trek: Voyager) |
E1008492
|
entity |
| Predicate | farewellTo |
P182152
|
FINISHED |
| Object | crew of Voyager |
—
|
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: crew of Voyager | Statement: [Homestead (Star Trek: Voyager), farewellTo, crew of Voyager]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: farewellTo Context triple: [Homestead (Star Trek: Voyager), farewellTo, crew of Voyager]
-
A.
farewellTour
Indicates that an entity is undertaking a final series of appearances, performances, or visits intended to mark its retirement or conclusion.
-
B.
awayFrom
Indicates that one entity is located at a distance from, or moving farther away from, another entity.
-
C.
departureStory
Indicates a narrative or account describing how, why, and under what circumstances an entity left or departed from a place, role, or situation.
-
D.
exitTo
Indicates that one location or entity serves as a passage or route leading directly to another location or entity.
-
E.
walkOff
Indicates that an entity departs or leaves a place or situation by walking away from it.
- 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_69f76dc78a308190a1ac29ad4a9a4895 |
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.