Triple
T1710840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oudezijds Voorburgwal |
E36978
|
entity |
| Predicate | hasWaterwayType |
P27890
|
FINISHED |
| Object | gracht |
—
|
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: gracht | Statement: [Oudezijds Voorburgwal, hasWaterwayType, gracht]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaterwayType Context triple: [Oudezijds Voorburgwal, hasWaterwayType, gracht]
-
A.
hasWatercourseType
chosen
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
-
B.
hasWaterwayRole
Indicates that an entity participates in or is associated with a waterway in a specific functional capacity or role.
-
C.
waterwayClass
Indicates the classification or type of a waterway based on its navigational, functional, or physical characteristics.
-
D.
hasStructureOnWatercourse
Indicates that a structure is physically located on, over, or directly associated with a specific watercourse.
-
E.
hasAreaWaterBody
Indicates that an entity includes, contains, or is associated with a body of water within its area or 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_69a88617439c819094ffb5d16a0f6307 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab7521878c8190b9e7739b8c3fc705 |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61bd46d48190915500d75a9d8e94 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.