Triple
T28163558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neckar basin |
E714960
|
entity |
| Predicate | mouthBasinOf |
P65489
|
FINISHED |
| Object | Rhine 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: Rhine River | Statement: [Neckar basin, mouthBasinOf, Rhine River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mouthBasinOf Context triple: [Neckar basin, mouthBasinOf, Rhine River]
-
A.
mouthBasinFor
Indicates that one entity serves as a basin or receptacle specifically intended for use with another entity’s mouth.
-
B.
basinPartOf
Indicates that one basin is a component or subdivision of a larger basin or basin system.
-
C.
basin
Indicates a geographic area where surface water drains into a common outlet, such as a river, lake, or ocean.
-
D.
basinServed
chosen
Indicates that a particular basin is supplied, drained, or otherwise functionally supported by another entity (such as a river, watershed, or infrastructure system).
-
E.
basinIncludesRegion
Indicates that a drainage basin or watershed spatially contains or encompasses a specified region within its boundaries.
- 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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f641ed2a0c81909246ce42d3e01317 |
completed | May 2, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:08 p.m.