Triple
T28221388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daubigny’s Garden |
E711465
|
entity |
| Predicate | creator’s birth name |
P6219
|
FINISHED |
| Object | Vincent Willem van Gogh |
—
|
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: Vincent Willem van Gogh | Statement: [Daubigny’s Garden, creator’s birth name, Vincent Willem van Gogh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creator’s birth name Context triple: [Daubigny’s Garden, creator’s birth name, Vincent Willem van Gogh]
-
A.
creatorBirthName
chosen
Indicates the full birth name originally given to the creator of a work or entity.
-
B.
authorBirthName
Indicates the full personal name an author was given at birth, before any later name changes or pseudonyms.
-
C.
authorRealNameOfCreator
Indicates that a person’s real, legal, or birth name is the true identity behind a creator who may be known by a pseudonym or handle.
-
D.
creatorGivenName
Indicates the given (first) name of the person or entity that created something.
-
E.
fictionalBirthName
Indicates the original personal name assigned to a fictional character at birth, as distinct from any later or alternate names they may use.
- 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_69efb51dfb048190ada79b745c33b363 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: April 27, 2026, 10:46 p.m.