Triple
T26941693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German Flatts, New York |
E678532
|
entity |
| Predicate | crossedByCanal |
P416
|
FINISHED |
| Object | Erie 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: Erie Canal | Statement: [German Flatts, New York, crossedByCanal, Erie Canal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossedByCanal Context triple: [German Flatts, New York, crossedByCanal, Erie Canal]
-
A.
hasCanalCrossing
Indicates that one entity is connected to or traversed by another via a canal crossing, such as a bridge, aqueduct, or similar structure over a canal.
-
B.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
-
C.
waterwayTypeCrossed
Indicates the specific kind of waterway (e.g., river, canal, stream) that is being crossed in the described relationship or action.
-
D.
crossesWaterBody
Indicates that an entity moves from one side of a water body to the other by passing over, through, or across it.
-
E.
crossedBy
chosen
Indicates that one entity (typically a path, line, or boundary) is intersected or traversed 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 6:18 a.m.