Triple
T12983615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schie waterway (as seen in View of Delft) |
E321712
|
entity |
| Predicate | foregrounds |
P107892
|
FINISHED |
| Object | city walls of Delft |
—
|
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: city walls of Delft | Statement: [Schie waterway (as seen in View of Delft), foregrounds, city walls of Delft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foregrounds Context triple: [Schie waterway (as seen in View of Delft), foregrounds, city walls of Delft]
-
A.
formerColor
Indicates that an entity previously had a certain color, but no longer has that color now.
-
B.
primaryFront
Indicates that one entity serves as the main or most important front-facing side or surface in relation to another entity.
-
C.
frontOf
Indicates that one entity is positioned directly before another along a primary viewing or movement direction.
-
D.
front
Indicates that one entity is located directly before or facing another entity along a primary viewing or movement direction.
-
E.
frontDesign
Indicates that one entity serves as the primary or visible front-facing design or appearance of another entity.
- F. None of above. chosen
Provenance (4 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97f2a71a0819098bb6cf8a4b2208a |
completed | April 10, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69d97dbdd94c8190ac4bbecca02dc77b |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97f1badac8190a59e60751f47b8d6 |
completed | April 10, 2026, 10:52 p.m. |
Created at: April 9, 2026, 8:39 p.m.