Triple
T29214645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portrait of Lady Hamilton as a Bacchante |
E740631
|
entity |
| Predicate | depictsRolePlay |
P17608
|
FINISHED |
| Object | historical costume portrait |
—
|
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: historical costume portrait | Statement: [Portrait of Lady Hamilton as a Bacchante, depictsRolePlay, historical costume portrait]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictsRolePlay Context triple: [Portrait of Lady Hamilton as a Bacchante, depictsRolePlay, historical costume portrait]
-
A.
depictsPersonRole
chosen
Indicates that an image or representation shows a person in a specific role, function, or capacity.
-
B.
roleOfCharacter
Indicates that one entity serves as the narrative or functional role played by a character within a story, scenario, or context.
-
C.
playRoleIn
Indicates that an entity participates in or performs a specific function, character, or part within an event, context, or system.
-
D.
portraysRoleTrait
Indicates that one entity depicts or represents a particular role or character trait of another entity.
-
E.
depicts
Indicates that one entity visually represents, portrays, or shows another entity.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 28, 2026, 12:12 p.m.