Triple
T14898094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mumuye |
E359930
|
entity |
| Predicate | artCollectedBy |
P23594
|
FINISHED |
| Object | Western museums |
—
|
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: Western museums | Statement: [Mumuye, artCollectedBy, Western museums]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artCollectedBy Context triple: [Mumuye, artCollectedBy, Western museums]
-
A.
artCollectionLaterHeldBy
Indicates that an art collection was initially owned or assembled by one party and subsequently came to be held or possessed by another party at a later time.
-
B.
collectedBy
chosen
Indicates that one entity has gathered, acquired, or assembled another entity, typically as part of a collection or data-gathering process.
-
C.
artCollectionFocus
Indicates that an art collection is primarily centered around or devoted to a particular theme, style, period, subject, or type of artwork.
-
D.
hasArtworksFrom
Indicates that one entity possesses or includes artworks that originate from or are created by another entity.
-
E.
hasArtCollection
Indicates that an entity possesses, maintains, or is associated with a collection of artworks.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded6084574819098033a9723f3e1c4 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:11 a.m.