Triple
T23384339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Millesgården Foundation |
E593834
|
entity |
| Predicate | overseesCollection |
P60724
|
FINISHED |
| Object | sculptures by Carl Milles |
—
|
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: sculptures by Carl Milles | Statement: [Millesgården Foundation, overseesCollection, sculptures by Carl Milles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overseesCollection Context triple: [Millesgården Foundation, overseesCollection, sculptures by Carl Milles]
-
A.
overseesCollectionType
chosen
Indicates that one entity has responsibility for supervising, managing, or administering a particular type or category of collection.
-
B.
overseesRepository
Indicates that one entity has responsibility for supervising, managing, or maintaining another entity’s repository.
-
C.
collectionFormed
Indicates that multiple items or entities have been gathered and organized together into a defined collection.
-
D.
collectionRepository
Indicates a relationship where a repository is responsible for storing, managing, or providing access to a collection.
-
E.
oversee
Indicates having responsibility for supervising, directing, or managing the actions or work of 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a497661c8190b52fa27419594989 |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:34 p.m.