Triple
T29208040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mukilteo–Clinton route |
E740468
|
entity |
| Predicate | usesVesselsFromClass |
P11945
|
FINISHED |
| Object | Issaquah-class ferries |
—
|
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: Issaquah-class ferries | Statement: [Mukilteo–Clinton route, usesVesselsFromClass, Issaquah-class ferries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesVesselsFromClass Context triple: [Mukilteo–Clinton route, usesVesselsFromClass, Issaquah-class ferries]
-
A.
usesVesselType
chosen
Indicates that an entity performs an activity or operation by employing a specific type or category of vessel.
-
B.
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.
-
C.
hasVesselType
Indicates that an entity is associated with or classified by a specific type of vessel (e.g., ship, boat, or container).
-
D.
usesVesselsOperatedBy
Indicates that one entity makes use of vessels that are operated or controlled by another entity.
-
E.
namedVesselOf
Indicates that one entity is the specific named vessel (e.g., ship, boat, or craft) associated with or belonging to 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 12:10 p.m.