Triple
T33461043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Where No Man Has Gone Before |
E856914
|
entity |
| Predicate | mainVessel |
P35755
|
FINISHED |
| Object | USS Enterprise (NCC-1701) |
—
|
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 Enterprise (NCC-1701) | Statement: [Where No Man Has Gone Before, mainVessel, USS Enterprise (NCC-1701)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainVessel Context triple: [Where No Man Has Gone Before, mainVessel, USS Enterprise (NCC-1701)]
-
A.
mainShip
chosen
Indicates that one entity serves as the primary or principal ship associated with another entity.
-
B.
primaryVessels
Indicates that the related vessels are the main or principal ones within a given system, structure, or context.
-
C.
hasVessel
Indicates that one entity possesses, uses, or is associated with a particular vessel (such as a container, ship, or transport medium) in the context of the described relationship or action.
-
D.
vesselFunction
Indicates that one entity serves as the functional role, purpose, or operational use of a vessel in relation to another entity.
-
E.
vesselService
Indicates a service relationship in which one entity provides, operates, or maintains a vessel (such as a ship or boat) for another entity.
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e4d2d66c819091d3c3a86ff2718e |
completed | May 3, 2026, 6:01 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:37 a.m.