Triple
T1241439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biobío River |
E26665
|
entity |
| Predicate | riverMouthLocation |
P3817
|
FINISHED |
| Object | near Concepción |
—
|
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: near Concepción | Statement: [Biobío River, riverMouthLocation, near Concepción]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverMouthLocation Context triple: [Biobío River, riverMouthLocation, near Concepción]
-
A.
mouthOfTheWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water.
-
B.
mouthOfWatercourse
chosen
Indicates the location where a watercourse ends and flows into a larger body of water or another watercourse.
-
C.
cityAtMouth
Indicates that a city is located at or very near the mouth (outlet) of a river.
-
D.
majorPortAtMouth
Indicates that a major port is located at the mouth of a river where it meets a larger body of water.
-
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_69a4948689d08190b3a4a3f388c02148 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf44ac3c8190a28a333b320305fd |
completed | March 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69a4bb696a38819095845c84f0241287 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.