Triple
T25225524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emissary (Star Trek: Deep Space Nine) |
E632076
|
entity |
| Predicate | connectsToEvent |
P10008
|
FINISHED |
| Object | Battle of Wolf 359 |
—
|
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: Battle of Wolf 359 | Statement: [Emissary (Star Trek: Deep Space Nine), connectsToEvent, Battle of Wolf 359]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsToEvent Context triple: [Emissary (Star Trek: Deep Space Nine), connectsToEvent, Battle of Wolf 359]
-
A.
connectedToEvent
chosen
Indicates that an entity has a direct association or linkage with a specific event.
-
B.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
C.
isLinkedToEvent
Indicates that an entity has an association or connection with a specific event.
-
D.
connectsToEventVenue
Indicates that one entity serves as a link or route providing access or connection to an event venue.
-
E.
connectsToSeries
Indicates that one entity is linked or associated with a particular series, establishing a connection or membership relationship between them.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 21, 2026, 1:03 p.m.