Triple
T29971274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ems River basin |
E761324
|
entity |
| Predicate | drainageRiverMouth |
P128783
|
FINISHED |
| Object | Ems River estuary |
—
|
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: Ems River estuary | Statement: [Ems River basin, drainageRiverMouth, Ems River estuary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drainageRiverMouth Context triple: [Ems River basin, drainageRiverMouth, Ems River estuary]
-
A.
riverMouthType
Indicates the type or form of the feature where a river meets a larger body of water.
-
B.
riverMouthAt
Indicates that the mouth or endpoint of a river is located at a specified place or geographic feature.
-
C.
riverMouthEmptiesInto
chosen
Indicates that the mouth of a river flows into and discharges its water into another body of water, such as a sea, ocean, lake, or another river.
-
D.
riverMouthBasin
Indicates that a river’s mouth lies within or drains into a particular drainage basin.
-
E.
riverMouthRegion
Indicates the region or area where a river flows into a larger body of water, such as a sea, lake, or another river.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6786e28848190b337f2e34b290f93 |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:32 p.m.