Triple
T33822457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helene Kröller-Müller |
E866864
|
entity |
| Predicate | notableArtistCollected |
P35859
|
FINISHED |
| Object | Vincent van Gogh |
E3276
|
NE 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: Vincent van Gogh | Statement: [Helene Kröller-Müller, notableArtistCollected, Vincent van Gogh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableArtistCollected Context triple: [Helene Kröller-Müller, notableArtistCollected, Vincent van Gogh]
-
A.
notableArtistInCollection
Indicates that an artist is prominently represented or recognized within a particular collection.
-
B.
notableArtist
Indicates that the subject is an artist who is widely recognized or distinguished for their work.
-
C.
notableArtistRosterCharacteristic
Indicates a distinguishing quality or feature that characterizes the roster of artists associated with an entity.
-
D.
notableMusician
Indicates that the subject is a musician who is widely recognized or distinguished for their musical work or impact.
-
E.
notableArtistRosterIncludes
chosen
Indicates that a notable artist is included as part of an entity’s recognized or distinguished roster of artists.
- F. None of above.
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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a366ea0cd6081908e966a41c64d29c8 |
completed | June 20, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:46 a.m.