Triple
T142847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erie Canal |
E2888
|
entity |
| Predicate | elevationChange |
P6813
|
FINISHED |
| Object | over 500 feet between Hudson River and Lake Erie |
—
|
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: over 500 feet between Hudson River and Lake Erie | Statement: [Erie Canal, elevationChange, over 500 feet between Hudson River and Lake Erie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationChange Context triple: [Erie Canal, elevationChange, over 500 feet between Hudson River and Lake Erie]
-
A.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
B.
typicalElevationRange
Indicates the usual range of elevation values within which something commonly occurs or exists.
-
C.
elevatedTo
Indicates that one entity is promoted or raised to a higher rank, status, position, or level relative to another.
-
D.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
E.
hasElevators
Indicates that one entity is equipped with or contains one or more elevators for vertical transportation.
- F. None of above. chosen
Provenance (4 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a2580ca15481909fa3e87d804a1b23 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a2565559ac81909e0c4e095a7dfa27 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2580b00988190868ee24c0289cf70 |
completed | Feb. 28, 2026, 2:50 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.