Triple
T4364239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky Dam |
E98733
|
entity |
| Predicate | riverMileFromMouth |
P55788
|
FINISHED |
| Object | 22.4 miles above the mouth of the Tennessee River |
—
|
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: 22.4 miles above the mouth of the Tennessee River | Statement: [Kentucky Dam, riverMileFromMouth, 22.4 miles above the mouth of the Tennessee River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverMileFromMouth Context triple: [Kentucky Dam, riverMileFromMouth, 22.4 miles above the mouth of the Tennessee River]
-
A.
riverMileBelowHooverDam
Indicates the position of a location along the river measured in miles downstream from Hoover Dam.
-
B.
riverMouthType
Indicates the type or form of the feature where a river meets a larger body of water.
-
C.
majorPortAtMouth
Indicates that a major port is located at the mouth of a river where it meets a larger body of water.
-
D.
cityAtMouth
Indicates that a city is located at or very near the mouth (outlet) of a river.
-
E.
mouthOfTheWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water.
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351e70a748190af6f1b709a0e75e6 |
completed | March 12, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:16 p.m.