Triple
T18304444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veenkoloniën |
E438445
|
entity |
| Predicate | hasPlanningStructure |
P56805
|
FINISHED |
| Object | canal-based colonization pattern |
—
|
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: canal-based colonization pattern | Statement: [Veenkoloniën, hasPlanningStructure, canal-based colonization pattern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlanningStructure Context triple: [Veenkoloniën, hasPlanningStructure, canal-based colonization pattern]
-
A.
plannedStructure
Indicates that one entity is a structure that is intended or designed to be built or established in the future, rather than already existing.
-
B.
hasPlanningLevel
Indicates that an entity is associated with a specific stage, tier, or granularity within a planning or scheduling hierarchy.
-
C.
hasPlanningConcept
chosen
Indicates that an entity is associated with, defined by, or governed by a particular planning-related concept or framework.
-
D.
hasPlanningType
Indicates that an entity is associated with a specific category or type used for planning or scheduling purposes.
-
E.
hasPlanningStatus
Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5018256508190b024980e3a4a3ae9 |
completed | April 19, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.