Triple
T19655501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hartford, Vermont |
E471928
|
entity |
| Predicate | locatedAtRiverConfluence |
P11842
|
FINISHED |
| Object | White 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: White River | Statement: [Hartford, Vermont, locatedAtRiverConfluence, White River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAtRiverConfluence Context triple: [Hartford, Vermont, locatedAtRiverConfluence, White River]
-
A.
locatedAtConfluenceOf
chosen
Indicates that something is situated at the meeting point where two or more bodies of water or similar flowing features join together.
-
B.
locatedOnBankOfRiver
Indicates that one entity is situated along or directly adjacent to the bank of a specified river.
-
C.
locatedBetweenRiver
Indicates that an entity is situated in the area or region between two segments or banks of a river, or between two rivers.
-
D.
locatedInRiverArea
Indicates that one entity is situated within the geographic area occupied by, adjacent to, or directly associated with a particular river.
-
E.
riverConfluence
Indicates the location or relationship where two or more rivers or streams join and merge into a single watercourse.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641452ac481908d5493506ee96516 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:45 p.m.