Triple
T30394768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sagamore (village) |
E773184
|
entity |
| Predicate | bridgeCrossingNearby |
P19223
|
FINISHED |
| Object | Cape Cod Canal |
—
|
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: Cape Cod Canal | Statement: [Sagamore (village), bridgeCrossingNearby, Cape Cod Canal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeCrossingNearby Context triple: [Sagamore (village), bridgeCrossingNearby, Cape Cod Canal]
-
A.
hasNearbyBridge
chosen
Indicates that one entity is located close to a bridge associated with or relevant to it.
-
B.
hasRiverCrossingNearby
Indicates that there is a river crossing located in close proximity to the referenced entity or location.
-
C.
hasBridgeCrossings
Indicates that one entity has one or more bridge structures that span across or connect over another entity (such as a road, river, or area).
-
D.
hasNearbyBridgeApproach
Indicates that one entity is located close to the approach section of a bridge associated with another entity.
-
E.
hasBridgeTypeCrossing
Indicates that a bridge is characterized by a specific type of crossing it provides or supports.
- 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f685ac63248190a51b9e0e6ed89dab |
completed | May 2, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:02 p.m.