Triple
T23459821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House at Keizersgracht 319 (attributed) |
E568935
|
entity |
| Predicate | hasDesignAttributionTo |
P184
|
FINISHED |
| Object | Philips Vingboons |
—
|
NE NERFINISHED |
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: Philips Vingboons | Statement: [House at Keizersgracht 319 (attributed), hasDesignAttributionTo, Philips Vingboons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDesignAttributionTo Context triple: [House at Keizersgracht 319 (attributed), hasDesignAttributionTo, Philips Vingboons]
-
A.
hasDesignRecognition
Indicates that an entity has received recognition, awards, or notable acknowledgment specifically for its design.
-
B.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
C.
designedBy
chosen
Indicates that one entity is the creator, planner, or architect responsible for the form or structure of another entity.
-
D.
hasDesignOrigin
Indicates that one entity is the source, inspiration, or original model from which the design of another entity is derived.
-
E.
hasDesignInputFrom
Indicates that the design of one entity is based on, influenced by, or derived from input provided by 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a69afba88190b1b1dd27d331309f |
completed | April 29, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:53 p.m.