Triple
T29926390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurâ |
E760090
|
entity |
| Predicate | isSpokenAlongRiver |
P168268
|
FINISHED |
| Object | Upper Xingu region |
—
|
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: Upper Xingu region | Statement: [Kurâ, isSpokenAlongRiver, Upper Xingu region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSpokenAlongRiver Context triple: [Kurâ, isSpokenAlongRiver, Upper Xingu region]
-
A.
hasSettlementOnRiver
Indicates that a settlement is located on or directly adjacent to a specific river.
-
B.
isOnlyNavigableRiverOf
Indicates that one river is the sole river that can be navigated within a specified area or context.
-
C.
isOnBorderRiver
Indicates that something is located along or directly adjacent to a river that forms a border between areas.
-
D.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
E.
hasFictionalRiver
Indicates that an entity includes, features, or is associated with a river that is fictional rather than real.
- 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67797fe5c81909575b762f32b63ef |
completed | May 2, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:16 p.m.