Triple
T34167456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ritthem |
E876449
|
entity |
| Predicate | isInRiverMouthRegion |
P57845
|
FINISHED |
| Object | Western Scheldt 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: Western Scheldt estuary | Statement: [Ritthem, isInRiverMouthRegion, Western Scheldt estuary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInRiverMouthRegion Context triple: [Ritthem, isInRiverMouthRegion, Western Scheldt estuary]
-
A.
riverMouthRegion
chosen
Indicates the region or area where a river flows into a larger body of water, such as a sea, lake, or another river.
-
B.
isTidalMouthOf
Indicates that one location is the tidal mouth or estuarine outlet through which a river or watercourse enters a larger body of water.
-
C.
hasIslandAtMouth
Indicates that a geographic feature, typically a river, has an island located at or near its mouth where it meets a larger body of water.
-
D.
isCoastalOrRiverine
Indicates that a place is located along a sea coast or adjacent to a river, reflecting a shoreline or riverbank relationship.
-
E.
riverMouthType
Indicates the type or form of the feature where a river meets a larger body of water.
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:54 a.m.