Triple
T38534048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | river March |
E923447
|
entity |
| Predicate | countriesInBasin |
P411
|
FINISHED |
| Object | Czech Republic |
E16450
|
NE 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: Czech Republic | Statement: [river March, countriesInBasin, Czech Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countriesInBasin Context triple: [river March, countriesInBasin, Czech Republic]
-
A.
basinCountry
chosen
Indicates the country or countries within whose territory a river basin or drainage area is primarily located or through which it significantly extends.
-
B.
countryDownstreamBasin
Indicates that one country lies within the downstream portion of a river basin relative to another country or reference point.
-
C.
reservoirCountry
Indicates that a country contains or hosts the reservoir associated with the referenced entity.
-
D.
riverMouthCountry
Indicates the country in which a river’s mouth (where it flows into another body of water) is located.
-
E.
bordersCountryViaWaterway
Indicates that two countries share a boundary that is defined or connected by a waterway such as a river, canal, or strait.
- F. None of above.
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_69f76ea8f6348190a5c03fb6292bbee3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a421bd4db7481908f266dee647979dd |
completed | June 29, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.