Triple
T333765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henri Matisse |
E6678
|
entity |
| Predicate | signatureWorkType |
P12509
|
FINISHED |
| Object | paper cut-outs |
—
|
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: paper cut-outs | Statement: [Henri Matisse, signatureWorkType, paper cut-outs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureWorkType Context triple: [Henri Matisse, signatureWorkType, paper cut-outs]
-
A.
signatureWork
Indicates that the work is a defining or most representative creation associated with an entity (such as a person, group, or organization).
-
B.
signatureStyle
Indicates the characteristic way in which an entity typically signs its name or marks documents, distinguishing its unique signing pattern or format.
-
C.
signatoryType
Indicates the specific role or category of a party that has signed or formally agreed to a document, contract, or agreement.
-
D.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
E.
signatureEvent
Indicates an event in which an entity formally signs or authorizes something, such as a document, agreement, or record.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eac4d9d081908a624464e450fb0e |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94d99cc8190a112e4b630ec63c1 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea7d03a88190aab72e61d8673488 |
completed | Feb. 28, 2026, 1:15 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.