Triple
T5490275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canals of Middelburg |
E123683
|
entity |
| Predicate | formsFeatureOf |
P9789
|
FINISHED |
| Object | old town of Middelburg |
—
|
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: old town of Middelburg | Statement: [Canals of Middelburg, formsFeatureOf, old town of Middelburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsFeatureOf Context triple: [Canals of Middelburg, formsFeatureOf, old town of Middelburg]
-
A.
formsFeature
chosen
Indicates that one entity constitutes or creates a characteristic, component, or distinguishing element of another entity.
-
B.
isFeatureOf
Indicates that something functions as a characteristic, attribute, or component belonging to or describing another entity.
-
C.
withinFeature
Indicates that one entity is spatially contained inside or lies entirely within the bounds of another feature.
-
D.
featureType
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
E.
nestFeature
Indicates that one entity is a structural or functional component contained within, or forming part of, 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_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927dcb848190a9d31e2435f8a755 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a8df6481908d1643f7342fe6f0 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:10 p.m.