Triple
T2036486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alplaus Kill |
E44640
|
entity |
| Predicate | hasMouthElevationApprox |
P35457
|
FINISHED |
| Object | low elevation near Mohawk River level |
—
|
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: low elevation near Mohawk River level | Statement: [Alplaus Kill, hasMouthElevationApprox, low elevation near Mohawk River level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMouthElevationApprox Context triple: [Alplaus Kill, hasMouthElevationApprox, low elevation near Mohawk River level]
-
A.
hasPortNearMouth
Indicates that an entity possesses a port or opening located close to its mouth region.
-
B.
mouthElevationBelowSeaLevel
Indicates that the elevation of the river’s mouth is below sea level.
-
C.
mouthNear
Indicates that one entity’s mouth is positioned close to another entity or object in space.
-
D.
mouthOf
Indicates the location where one entity (typically a river or similar feature) empties into or opens out into another, larger body or feature.
-
E.
elevationBy
Indicates a relationship where one entity raises, increases, or enhances the level, status, or intensity of another entity.
- 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_69a889159ec481908f9e4472d9f480c7 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9363b608190b42aa6d3f3fd78c4 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb90ec7948190bbfb0329e9e67cca |
completed | March 7, 2026, 5:35 a.m. |
Created at: March 4, 2026, 7:39 p.m.