Triple
T35859438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ondava basin |
E1036904
|
entity |
| Predicate | collectsWatersFrom |
P138393
|
FINISHED |
| Object | Ondava 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: Ondava River | Statement: [Ondava basin, collectsWatersFrom, Ondava River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectsWatersFrom Context triple: [Ondava basin, collectsWatersFrom, Ondava River]
-
A.
collectsSurfaceWaterFrom
chosen
Indicates that one entity gathers or receives surface water (such as runoff, streams, or overland flow) originating from another entity.
-
B.
feedsWatersThatReach
Indicates that one body of water supplies or contributes flow to other waters that it eventually reaches.
-
C.
receivesFreshwaterFrom
Indicates that one entity is supplied with or obtains freshwater from another entity as its source.
-
D.
collectsRainfallFor
Indicates that one entity gathers or measures rainfall on behalf of, or for the benefit of, another entity.
-
E.
transportsWaterFrom
Indicates that one entity carries or conveys water from a specified source entity to another location or entity.
- 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 3, 2026, 4:06 p.m.