Triple
T17576076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David (bronze) |
E428072
|
entity |
| Predicate | locatedInMuseumCollection |
P32052
|
FINISHED |
| Object | Bargello sculpture collection |
—
|
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: Bargello sculpture collection | Statement: [David (bronze), locatedInMuseumCollection, Bargello sculpture collection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInMuseumCollection Context triple: [David (bronze), locatedInMuseumCollection, Bargello sculpture collection]
-
A.
museumHolds
chosen
Indicates that a museum possesses, preserves, or has custody of a particular item or collection within its holdings.
-
B.
museumAt
Indicates that an entity (such as an exhibit, artifact, or event) is located at or associated with a particular museum.
-
C.
inMuseumCollectionSince
Indicates the date or time from which an item has been part of a museum’s collection.
-
D.
associatedWithMuseum
Indicates a relationship where an entity has a formal or recognized connection to a museum, such as ownership, curation, exhibition, or institutional affiliation.
-
E.
hasMuseumAt
Indicates that a museum is located at or exists in a specified place or location.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e463c88b3081908ddf6a2a12f6138e |
completed | April 19, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fd7d048190b54ee4c6155612a5 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.