Triple
T29208056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mukilteo–Clinton route |
E740468
|
entity |
| Predicate | hasTerminalUpgrade |
P111167
|
FINISHED |
| Object | Mukilteo multimodal ferry terminal |
—
|
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: Mukilteo multimodal ferry terminal | Statement: [Mukilteo–Clinton route, hasTerminalUpgrade, Mukilteo multimodal ferry terminal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerminalUpgrade Context triple: [Mukilteo–Clinton route, hasTerminalUpgrade, Mukilteo multimodal ferry terminal]
-
A.
hasUpgrade
Indicates that one entity possesses, includes, or is associated with an improved or enhanced version of another entity.
-
B.
hasUpgradeSystem
Indicates that an entity includes or is equipped with a system for performing upgrades or enhancements.
-
C.
hasUpgradeProject
chosen
Indicates that an entity is associated with a project whose purpose is to improve, enhance, or modernize that entity.
-
D.
upgradeEligibility
Indicates whether an entity qualifies to move from its current version, level, or plan to a higher or more advanced one under defined criteria.
-
E.
mayBeUpgradedTo
Indicates that one entity is eligible or allowed to be changed into a higher, improved, or more advanced version represented by 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_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 28, 2026, 12:10 p.m.