Triple
T32022511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louvre INV 1980 |
E817731
|
entity |
| Predicate | inventoryNumberFor |
P116155
|
FINISHED |
| Object | Madonna of Chancellor Rolin |
—
|
NE NERFINISHED |
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: Madonna of Chancellor Rolin | Statement: [Louvre INV 1980, inventoryNumberFor, Madonna of Chancellor Rolin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inventoryNumberFor Context triple: [Louvre INV 1980, inventoryNumberFor, Madonna of Chancellor Rolin]
-
A.
inventoryNumberAt
Indicates that a specific inventory number is assigned to an entity at a particular location or point in time.
-
B.
inventoryNumberOf
chosen
Indicates that one entity is the inventory or catalog number assigned to another entity.
-
C.
ISONumber
Indicates that an entity is associated with, identified by, or conforms to a specific ISO (International Organization for Standardization) number or standard.
-
D.
isNumberedBy
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
E.
inscriptionNumber
Indicates the identifying number assigned to a specific inscription within a collection or system.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b467759c8190905ba0ce0eceb5fb |
completed | May 3, 2026, 2:35 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:17 a.m.