Triple
T2825714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monongahela River |
E54914
|
entity |
| Predicate | elevationAtMouth |
P40408
|
FINISHED |
| Object | approximately 710 feet |
—
|
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: approximately 710 feet | Statement: [Monongahela River, elevationAtMouth, approximately 710 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationAtMouth Context triple: [Monongahela River, elevationAtMouth, approximately 710 feet]
-
A.
riverMouthElevation
chosen
Indicates the elevation at which a river reaches its mouth or endpoint, typically where it flows into another body of water.
-
B.
mouthElevationBelowSeaLevel
Indicates that the elevation of the river’s mouth is below sea level.
-
C.
majorPortAtMouth
Indicates that a major port is located at the mouth of a river where it meets a larger body of water.
-
D.
elevationAtBase
Indicates the height or altitude measured at the base or lowest point of an object or feature relative to a reference level.
-
E.
elevationAboveLake
Indicates the vertical height or altitude of something relative to the surface level of a specified lake.
- 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_69ab49e100c0819082a40cb797383243 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde925e688190bb390d3182f8c4f0 |
completed | March 7, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_69abdd0acab881909e8c25cbef83678c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.