Triple
T11051238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mukilteo–Clinton |
E261255
|
entity |
| Predicate | primaryVesselType |
P11945
|
FINISHED |
| Object | ferry |
—
|
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: ferry | Statement: [Mukilteo–Clinton, primaryVesselType, ferry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryVesselType Context triple: [Mukilteo–Clinton, primaryVesselType, ferry]
-
A.
primaryVessels
Indicates that the related vessels are the main or principal ones within a given system, structure, or context.
-
B.
maximumVesselType
Indicates the highest or largest class, size, or category of vessel that is allowed, applicable, or associated in a given context.
-
C.
hasVesselType
Indicates that an entity is associated with or classified by a specific type of vessel (e.g., ship, boat, or container).
-
D.
usesVesselType
chosen
Indicates that an entity performs an activity or operation by employing a specific type or category of vessel.
-
E.
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.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798698bd88190aa97afd37f55e19f |
completed | April 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.