Triple
T30623308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Suicide of Dorothy Hale |
E779504
|
entity |
| Predicate | inscriptionPosition |
P23382
|
FINISHED |
| Object | lower part of the painting |
—
|
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: lower part of the painting | Statement: [The Suicide of Dorothy Hale, inscriptionPosition, lower part of the painting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscriptionPosition Context triple: [The Suicide of Dorothy Hale, inscriptionPosition, lower part of the painting]
-
A.
inscriptionLayout
Indicates how an inscription is spatially arranged or formatted in relation to the surface or object it appears on.
-
B.
inscriptionFeature
Indicates that one entity bears or contains an inscribed element or marking that is treated as a notable feature in relation to another entity.
-
C.
inscriptionLocation
chosen
Indicates the place or surface on which an inscription is written or engraved.
-
D.
inscriptionSide
Indicates the specific side or face of an object on which an inscription is located.
-
E.
inscriptionType
Indicates the specific kind or category of inscription associated with an entity (e.g., dedicatory, funerary, commemorative).
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a17ccc88190b6e8203a8b4cfd22 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:27 p.m.