Triple
T10760234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oude Pekela |
E253805
|
entity |
| Predicate | hasCanalSideDevelopment |
P25009
|
FINISHED |
| Object | linear settlement along Pekelderdiep |
—
|
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: linear settlement along Pekelderdiep | Statement: [Oude Pekela, hasCanalSideDevelopment, linear settlement along Pekelderdiep]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanalSideDevelopment Context triple: [Oude Pekela, hasCanalSideDevelopment, linear settlement along Pekelderdiep]
-
A.
hasCanals
Indicates that one entity possesses or contains canals, either as physical waterways or channel-like structures.
-
B.
hasMajorCanal
Indicates that one entity possesses or contains a primary canal or main waterway associated with it.
-
C.
hasWaterfrontDevelopment
chosen
Indicates that a location or property includes or is associated with constructed developments directly along or adjacent to a body of water.
-
D.
hasCanalsideSetting
Indicates that one entity is situated directly alongside or adjacent to a canal.
-
E.
hasAdjacentCanal
Indicates that one entity is directly next to or alongside a canal.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d731a14c7481909c6f4f9b15dc130f |
completed | April 9, 2026, 4:57 a.m. |
| PD | Predicate disambiguation | batch_69d6f311529c819080ca5493d55d6050 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.