Triple
T29208055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mukilteo–Clinton route |
E740468
|
entity |
| Predicate | isYearRoundService |
P84440
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mukilteo–Clinton route, isYearRoundService, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isYearRoundService Context triple: [Mukilteo–Clinton route, isYearRoundService, true]
-
A.
isUsedAllYear
Indicates that something is utilized or remains in active use throughout the entire year, without being limited to a particular season or period.
-
B.
isSeasonalStandard
Indicates that something follows or conforms to the standard conditions, rules, or patterns that apply only during a specific season or time period.
-
C.
isYearRoundCommunity
Indicates that a place or settlement is inhabited and functions as a community throughout the entire year, rather than only seasonally or temporarily.
-
D.
accessibleYearRound
chosen
Indicates that the subject can be accessed or used during all seasons of the year without interruption.
-
E.
hasWeekdayService
Indicates that a service operates on weekdays (typically Monday through Friday).
- 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_69f66402f5348190be752c897f8e5e2d |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:10 p.m.