Triple
T12983618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schie waterway (as seen in View of Delft) |
E321712
|
entity |
| Predicate | hasElementDepicted |
P46781
|
FINISHED |
| Object | moored boats |
—
|
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: moored boats | Statement: [Schie waterway (as seen in View of Delft), hasElementDepicted, moored boats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElementDepicted Context triple: [Schie waterway (as seen in View of Delft), hasElementDepicted, moored boats]
-
A.
canBeDepictedAs
Indicates that one entity is capable of being visually represented or illustrated in the form or style of another entity.
-
B.
depictionElement
chosen
Indicates that one entity is an element or component that appears within the visual or representational depiction of another entity.
-
C.
hasExhibitElement
Indicates that something (such as an exhibit or display) includes or is composed of a particular element or component.
-
D.
hasChainDepicted
Indicates that an entity has a chain (or chains) visually represented as part of its depiction.
-
E.
hasNoDepictionOf
Indicates that the subject lacks any visual or graphical representation of the specified object or concept.
- 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_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. |
Created at: April 9, 2026, 8:39 p.m.