Triple
T19048502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kitchen (Thomas Demand) |
E466196
|
entity |
| Predicate | signatureCharacteristics |
P51216
|
FINISHED |
| Object | absence of human figures |
—
|
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: absence of human figures | Statement: [Kitchen (Thomas Demand), signatureCharacteristics, absence of human figures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureCharacteristics Context triple: [Kitchen (Thomas Demand), signatureCharacteristics, absence of human figures]
-
A.
signatureFeature
chosen
Indicates that one entity is a defining or characteristic feature that distinctly identifies or typifies another entity.
-
B.
signaturePersona
Indicates that an entity serves as the primary or defining persona, identity, or character most closely associated with another entity.
-
C.
signatureVariant
Indicates that one signature is an alternative or modified form of another signature, differing in some aspect such as content, format, or representation while remaining related.
-
D.
signFeature
Indicates that an entity bears or displays a particular sign, symbol, or distinguishing feature.
-
E.
signatureStyle
Indicates the characteristic way in which an entity typically signs its name or marks documents, distinguishing its unique signing pattern or format.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d8062ea481908cf3fcb790a74956 |
completed | April 20, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.