Triple
T24476145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Litta Madonna |
E617237
|
entity |
| Predicate | transferHistory |
P156251
|
FINISHED |
| Object | transferred from panel to canvas |
—
|
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: transferred from panel to canvas | Statement: [Litta Madonna, transferHistory, transferred from panel to canvas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferHistory Context triple: [Litta Madonna, transferHistory, transferred from panel to canvas]
-
A.
operatorHistory
Indicates a record of past actions, states, or changes associated with a particular operator over time.
-
B.
storageHistory
Indicates the record of how something has been stored over time, including past storage conditions, locations, or states.
-
C.
hasDenominationHistory
Indicates that an entity has an associated record or sequence of changes in its denomination over time.
-
D.
ownershipHistory
Indicates the sequence of past and present owners associated with an entity over time.
-
E.
hasSettlementHistory
Indicates that an entity has a documented history of human settlement or habitation in relation to another entity (such as a place or time period).
- 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_69e2d7f3ae788190b683394db15f220e |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2994820f0819096f04d72ee2f4258 |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:21 a.m.