Triple
T12374533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edwards Dam |
E295087
|
entity |
| Predicate | riverMouthUpstreamDistance |
P55788
|
FINISHED |
| Object | 27 miles from the mouth of the Kennebec 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: 27 miles from the mouth of the Kennebec River | Statement: [Edwards Dam, riverMouthUpstreamDistance, 27 miles from the mouth of the Kennebec River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverMouthUpstreamDistance Context triple: [Edwards Dam, riverMouthUpstreamDistance, 27 miles from the mouth of the Kennebec River]
-
A.
riverMileFromMouth
chosen
Indicates the distance, measured in river miles, from the river’s mouth upstream to a specific point along the river.
-
B.
riverMouthBasin
Indicates that a river’s mouth lies within or drains into a particular drainage basin.
-
C.
riverMouthType
Indicates the type or form of the feature where a river meets a larger body of water.
-
D.
riverMouthRegion
Indicates the region or area where a river flows into a larger body of water, such as a sea, lake, or another river.
-
E.
riverLocation
Indicates that a river is located in, passes through, or is geographically associated with a specified place or region.
- 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_69d6ab6d8a4081908636601e69ddf262 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93fa8ca7c8190b3f8e9c2ec23e837 |
completed | April 10, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.