Triple
T31236623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Juan Channel |
E796441
|
entity |
| Predicate | nearbyPortOrHarbor |
P42191
|
FINISHED |
| Object | Friday Harbor |
—
|
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: Friday Harbor | Statement: [San Juan Channel, nearbyPortOrHarbor, Friday Harbor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyPortOrHarbor Context triple: [San Juan Channel, nearbyPortOrHarbor, Friday Harbor]
-
A.
nearbyPortFacility
Indicates that one entity is located close to or in the immediate vicinity of a port facility.
-
B.
hasNearbyHarbor
chosen
Indicates that one location has a harbor situated close to it in geographic proximity.
-
C.
nearbyCityOrPort
Indicates that one location is geographically close to a city or port, typically within a short travel distance.
-
D.
hasNearbyFerryPort
Indicates that one location is situated close enough to another location that serves as a ferry port to be considered nearby.
-
E.
nearestMajorPort
Indicates the closest significant seaport to a given location or entity, typically based on geographic distance.
- 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_69f224db69ac81909a370adad6a7ac7c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: April 29, 2026, 9:11 p.m.