Triple
T24882381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pomeroon-Supenaam |
E622747
|
entity |
| Predicate | hasRiverineCommunitiesOn |
P133853
|
FINISHED |
| Object | Pomeroon 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: Pomeroon River | Statement: [Pomeroon-Supenaam, hasRiverineCommunitiesOn, Pomeroon River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverineCommunitiesOn Context triple: [Pomeroon-Supenaam, hasRiverineCommunitiesOn, Pomeroon River]
-
A.
hasRiverCommunity
chosen
Indicates that there is a community located along, dependent on, or closely associated with a particular river.
-
B.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
C.
hasTownOnRiver
Indicates that a town is situated on or directly adjacent to a particular river.
-
D.
isSharedFreshwaterResourceOf
Indicates that a freshwater resource (such as a river, lake, or aquifer) is jointly used, managed, or claimed by multiple parties (e.g., states, regions, or communities).
-
E.
hasRiverIslands
Indicates that a river contains one or more islands within its course or channel.
- 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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 5:24 a.m.