Triple
T25293645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Trek: Vanguard |
E634155
|
entity |
| Predicate | stationDesignation |
P8935
|
FINISHED |
| Object | Starbase 47 |
—
|
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: Starbase 47 | Statement: [Star Trek: Vanguard, stationDesignation, Starbase 47]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stationDesignation Context triple: [Star Trek: Vanguard, stationDesignation, Starbase 47]
-
A.
clusterDesignation
Indicates that an entity is assigned to or identified as part of a specific cluster or grouping.
-
B.
stateDesignation
Indicates that an entity has been formally assigned or recognized with a particular status, title, or classification by an official authority or governing body.
-
C.
stationName
chosen
Indicates the name assigned to a particular station in the relationship.
-
D.
mapDesignation
Indicates a formal label or identifier that is assigned to something specifically for use on a map.
-
E.
systemDesignation
Indicates that an entity has been assigned a specific formal label or identifier within a defined system or framework.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 1:22 p.m.