Triple
T24840995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inga II Dam |
E621611
|
entity |
| Predicate | locatedAtRapids |
P73621
|
FINISHED |
| Object | Inga Falls |
—
|
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: Inga Falls | Statement: [Inga II Dam, locatedAtRapids, Inga Falls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAtRapids Context triple: [Inga II Dam, locatedAtRapids, Inga Falls]
-
A.
locatedAtConfluenceOf
Indicates that something is situated at the meeting point where two or more bodies of water or similar flowing features join together.
-
B.
locatedInRiverArea
chosen
Indicates that one entity is situated within the geographic area occupied by, adjacent to, or directly associated with a particular river.
-
C.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
D.
locatedAlong
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
-
E.
oftenLocatedAt
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
- 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 18, 2026, 5:18 a.m.