Triple
T23474070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hood Canal Bridge |
E570210
|
entity |
| Predicate | connectsCityNear |
P134094
|
FINISHED |
| Object | Port Gamble area |
—
|
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: Port Gamble area | Statement: [Hood Canal Bridge, connectsCityNear, Port Gamble area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsCityNear Context triple: [Hood Canal Bridge, connectsCityNear, Port Gamble area]
-
A.
connectsCity
Indicates a relationship where one entity serves as a link or route that joins or provides direct access between two cities.
-
B.
nearbyUrbanCenter
Indicates that one location is geographically close to an urban center, such as a city or large town.
-
C.
connectsAreaNear
chosen
Indicates that one entity serves as a link or passage between areas that are geographically close to each other.
-
D.
nearbyUse
Indicates that one entity uses or operates another entity that is located nearby or in close physical proximity.
-
E.
infrastructureNearby
Indicates that one entity is located close to another entity that serves as infrastructure (such as roads, utilities, or public facilities).
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a70363488190bcbdedec5c2a945c |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:59 p.m.