Triple
T25973167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hantes |
E645862
|
entity |
| Predicate | countryOfRiverMouth |
P87832
|
FINISHED |
| Object | Belgium |
—
|
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: Belgium | Statement: [Hantes, countryOfRiverMouth, Belgium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOfRiverMouth Context triple: [Hantes, countryOfRiverMouth, Belgium]
-
A.
riverMouthCountry
chosen
Indicates the country in which a river’s mouth (where it flows into another body of water) is located.
-
B.
страна устья
Indicates a relationship where a country is associated with or contains the mouth (outflow point) of a river.
-
C.
basinCountry
Indicates the country or countries within whose territory a river basin or drainage area is primarily located or through which it significantly extends.
-
D.
reservoirCountry
Indicates that a country contains or hosts the reservoir associated with the referenced entity.
-
E.
riverMouthAt
Indicates that the mouth or endpoint of a river is located at a specified place or geographic feature.
- 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 22, 2026, 8:51 a.m.