Triple
T18447946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ribeira da Torre |
E450705
|
entity |
| Predicate | drainsNear |
P131661
|
FINISHED |
| Object | town of Ribeira Grande |
—
|
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: town of Ribeira Grande | Statement: [Ribeira da Torre, drainsNear, town of Ribeira Grande]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drainsNear Context triple: [Ribeira da Torre, drainsNear, town of Ribeira Grande]
-
A.
dischargesNear
Indicates that one entity releases or emits something in close spatial proximity to another entity.
-
B.
drainsAreaOf
Indicates that one entity serves as a drainage outlet or basin for another entity, carrying away its surface or groundwater.
-
C.
drainageBetween
Indicates that one area or feature serves as a drainage path or channel between two other areas or features, allowing water or runoff to flow from one to the other.
-
D.
drainsInto
Indicates that one entity serves as a source or conduit whose contents or flow are directed into another entity.
-
E.
nearbyBasin
Indicates that one basin is located close to another basin in space.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52645cb88819086b0e70b6613edcd |
completed | April 19, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:30 a.m.