Triple
T31486815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarouca Municipality |
E803296
|
entity |
| Predicate | hasMainRiverNearby |
P165
|
FINISHED |
| Object | Varosa 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: Varosa River | Statement: [Tarouca Municipality, hasMainRiverNearby, Varosa River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainRiverNearby Context triple: [Tarouca Municipality, hasMainRiverNearby, Varosa River]
-
A.
hasNearbyRiverStructure
Indicates that a river-related structure (such as a dam, bridge, or levee) is located close to the referenced entity.
-
B.
hasRiver
chosen
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
C.
hasMajorTownOnRiver
Indicates that a major town is located on and directly associated with a particular river.
-
D.
riverTypeNearby
Indicates that one entity is located near a river of a specified type or classification.
-
E.
distanceToMajorRiver
Indicates the measured distance between a given location or entity and the nearest major river.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a002ae74da08190a4b47e0ff0f7f8fe |
completed | May 10, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_6a0029cc369c81909578e52c4a75ab18 |
completed | May 10, 2026, 6:46 a.m. |
Created at: April 30, 2026, 9:35 p.m.