Triple
T31008465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Oconee River |
E790139
|
entity |
| Predicate | formedOconeeRiverWith |
P198995
|
FINISHED |
| Object | Middle Oconee River |
—
|
NE NERFINISHED |
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: Middle Oconee River | Statement: [North Oconee River, formedOconeeRiverWith, Middle Oconee River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedOconeeRiverWith Context triple: [North Oconee River, formedOconeeRiverWith, Middle Oconee River]
-
A.
locatedOnTributaryOf
Indicates that one entity is situated along or on the banks of a tributary that flows into another specified water body.
-
B.
reachedRiver
Indicates that an entity has arrived at or come into contact with a river as a result of movement or travel.
-
C.
tookPlaceOnRiver
Indicates that an event or action occurred on or along a specific river.
-
D.
operatesOnRiver
Indicates that an entity conducts its operations or activities on, along, or directly involving a river.
-
E.
reachedOhioRiver
Indicates that an entity has arrived at or come to the Ohio River as a destination or waypoint.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
| PDg | Predicate description generation | batch_69ff1a95b6fc81909331bb03e263b5b9 |
completed | May 9, 2026, 11:29 a.m. |
Created at: April 29, 2026, 8:57 p.m.