Triple
T38475954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transportation in Kitsap County, Washington |
E915549
|
entity |
| Predicate | includesFerryOperator |
P5933
|
FINISHED |
| Object | Washington State Ferries |
E39517
|
NE 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: Washington State Ferries | Statement: [Transportation in Kitsap County, Washington, includesFerryOperator, Washington State Ferries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesFerryOperator Context triple: [Transportation in Kitsap County, Washington, includesFerryOperator, Washington State Ferries]
-
A.
ferryOperator
chosen
Indicates that one entity operates, manages, or runs a ferry service for another entity or in a particular context.
-
B.
ferryOperatorType
Indicates the type or category of operator responsible for running a ferry service.
-
C.
shipOperator
Indicates the entity that is responsible for operating, managing, or running a ship.
-
D.
hasFerryType
Indicates that an entity (such as a ferry route or service) is associated with a specific type or category of ferry.
-
E.
hasFerryComponent
Indicates that something includes or is associated with a ferry-related part, feature, or segment within its structure or operation.
- F. None of above.
Provenance (4 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41ccbec9948190aa200f63d70381c3 |
completed | June 29, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.