Triple
T16883724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scherpenzeel |
E421484
|
entity |
| Predicate | isInRiverArea |
P73621
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
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: true | Statement: [Scherpenzeel, isInRiverArea, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInRiverArea Context triple: [Scherpenzeel, isInRiverArea, true]
-
A.
locatedInRiverArea
chosen
Indicates that one entity is situated within the geographic area occupied by, adjacent to, or directly associated with a particular river.
-
B.
isOnWatercourse
Indicates that one entity is situated directly on, above, or along the path of a watercourse such as a river, stream, or canal.
-
C.
isInWaterwaySystem
Indicates that an entity is part of, contained within, or traverses a particular waterway network or system.
-
D.
isInLake
Indicates that one entity is located within the body of water defined as a lake.
-
E.
hasFloodplain
Indicates that an area or location lies within the floodplain associated with a particular water body or flooding source.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3bbbf0cec819084216807601afad1 |
completed | April 18, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.