Triple
T29932058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beverwaard |
E760240
|
entity |
| Predicate | locatedInRiverIslandRegion |
P156002
|
FINISHED |
| Object | IJsselmonde island |
—
|
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: IJsselmonde island | Statement: [Beverwaard, locatedInRiverIslandRegion, IJsselmonde island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInRiverIslandRegion Context triple: [Beverwaard, locatedInRiverIslandRegion, IJsselmonde island]
-
A.
locatedInRiverArea
Indicates that one entity is situated within the geographic area occupied by, adjacent to, or directly associated with a particular river.
-
B.
isOnRiverIsland
chosen
Indicates that one entity (typically a place or structure) is located on an island situated within a river.
-
C.
locatedBetweenRiver
Indicates that an entity is situated in the area or region between two segments or banks of a river, or between two rivers.
-
D.
locatedOnBankOfRiver
Indicates that one entity is situated along or directly adjacent to the bank of a specified river.
-
E.
locatedAcrossRiverFrom
Indicates that one entity is situated on the opposite side of a river relative to another entity.
- 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a007338002081908cb6340d65ff86d5 |
completed | May 10, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_6a0072a137ac8190a7debeb28e738e03 |
completed | May 10, 2026, 11:57 a.m. |
Created at: April 29, 2026, 6:18 p.m.