Triple
T16971619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portrait of a Gentleman |
E411696
|
entity |
| Predicate | refinedStyle |
P125442
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Portrait of a Gentleman, refinedStyle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refinedStyle Context triple: [Portrait of a Gentleman, refinedStyle, true]
-
A.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an entity.
-
B.
styleInFull
Indicates that something is presented, written, or expressed in its complete, unabbreviated, or fully detailed form.
-
C.
styleFor
Indicates a relationship where one entity defines, specifies, or is used as the style or styling configuration applied to another entity.
-
D.
broughtStyleTo
Indicates that one entity introduced or contributed a particular style or aesthetic to another entity or context.
-
E.
inTheStyleOf
Indicates that one entity is created, performed, or presented in a manner that imitates or closely resembles the characteristic style of another entity.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0ad04ac81909a11b45be567613a |
completed | April 18, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:31 a.m.