Triple
T8407264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Chipperfield |
E198529
|
entity |
| Predicate | curatedInYear |
P21264
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [David Chipperfield, curatedInYear, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curatedInYear Context triple: [David Chipperfield, curatedInYear, 2012]
-
A.
curatedIn
Indicates that an entity has been intentionally selected, organized, or managed for inclusion within a particular collection, exhibition, or curated context.
-
B.
curatedAt
chosen
Indicates the time or context at which an item was intentionally selected, organized, or assembled as part of a curated collection or set.
-
C.
collectedInPublicationYear
Indicates that the collecting event or data record was documented in a publication that appeared in the specified year.
-
D.
catalogueInclusionYear
Indicates the year in which an item was first included or recorded in a catalogue.
-
E.
foundInYear
Indicates the specific calendar year in which something was discovered, created, established, or otherwise found.
- 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_69ca8310df9c8190b25f16161cca3e41 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb831409308190981089c303ebaef4 |
completed | March 31, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69cb70d473dc8190af8ea81ee5aa970d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:05 p.m.