Triple
T28402865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomb of Vincent van Gogh |
E719436
|
entity |
| Predicate | hasRelativeBuriedNearby |
P90545
|
FINISHED |
| Object | Theo 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: Theo van Gogh | Statement: [Tomb of Vincent van Gogh, hasRelativeBuriedNearby, Theo van Gogh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelativeBuriedNearby Context triple: [Tomb of Vincent van Gogh, hasRelativeBuriedNearby, Theo van Gogh]
-
A.
hasMemberBuriedAt
Indicates that a group, organization, or family has at least one of its members buried at a specified burial place or site.
-
B.
buriedNear
chosen
Indicates that one entity is interred or buried in close physical proximity to another entity.
-
C.
isBuriedIn
Indicates that one entity is located beneath the ground or enclosed within another entity, typically as in a grave, tomb, or burial site.
-
D.
hasBuriedRemains
Indicates that one entity contains or is the location of the buried remains of another entity.
-
E.
buriedFor
Indicates that one entity is buried on behalf of, in honor of, or as a memorial for 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69ff519b65f081909902ba83b775ef85 |
completed | May 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69ff506fccdc8190bd93269589040aed |
completed | May 9, 2026, 3:19 p.m. |
Created at: April 28, 2026, 1:21 a.m.