Triple
T43407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Self-Portrait with a Straw Hat |
E853
|
entity |
| Predicate | hasTechnique |
P3047
|
FINISHED |
| Object | short, energetic brushstrokes |
—
|
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: short, energetic brushstrokes | Statement: [Self-Portrait with a Straw Hat, hasTechnique, short, energetic brushstrokes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTechnique Context triple: [Self-Portrait with a Straw Hat, hasTechnique, short, energetic brushstrokes]
-
A.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
B.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
C.
hasTechnicalSociety
Indicates that an entity is associated with, or possesses membership in, a technical or engineering-focused society or organization.
-
D.
hasTechnicalCommittee
Indicates that an entity is associated with or overseen by a specific technical committee.
-
E.
hasConcept
Indicates that an entity includes, embodies, or is associated with a particular concept.
- 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_69a247a8f6c08190bac804906d62ed5a |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24c083ad081909c1122c8fb29efdc |
completed | Feb. 28, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69a24aba9a2c81909f769a8f22e30c92 |
completed | Feb. 28, 2026, 1:54 a.m. |
| PDg | Predicate description generation | batch_69a24c0794c0819095509d970e05fc0f |
completed | Feb. 28, 2026, 1:59 a.m. |
Created at: Feb. 28, 2026, 1:46 a.m.