Triple
T4454966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mechanicville, New York |
E97697
|
entity |
| Predicate | waterwayFeature |
P31054
|
FINISHED |
| Object | Champlain Canal vicinity |
—
|
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: Champlain Canal vicinity | Statement: [Mechanicville, New York, waterwayFeature, Champlain Canal vicinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterwayFeature Context triple: [Mechanicville, New York, waterwayFeature, Champlain Canal vicinity]
-
A.
riverFeatureType
Indicates the specific kind or category of physical or functional feature associated with a river (e.g., source, mouth, tributary, channel segment).
-
B.
waterwaySystem
Indicates that one entity is part of, or belongs to, a connected network of waterways associated with another entity.
-
C.
waterwayClass
Indicates the classification or type of a waterway based on its navigational, functional, or physical characteristics.
-
D.
waterwayJunction
Indicates a point where two or more waterways meet, intersect, or branch from one another.
-
E.
hydrologyFeature
chosen
Indicates a relationship where one entity is a hydrological feature (such as a body or flow of water) associated with or characterizing 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_69b3454777808190b78aa9047ba1f018 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355f79ca481909338dda9f4f7171f |
completed | March 13, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69b34f649df081909d3cc2f6a1b8f282 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:33 p.m.