Triple
T17979022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tomb of Anthonie van Leeuwenhoek |
E449550
|
entity |
| Predicate | hasNearbyGrave |
P90545
|
FINISHED |
| Object | tomb of Johannes Vermeer |
—
|
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: tomb of Johannes Vermeer | Statement: [tomb of Anthonie van Leeuwenhoek, hasNearbyGrave, tomb of Johannes Vermeer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyGrave Context triple: [tomb of Anthonie van Leeuwenhoek, hasNearbyGrave, tomb of Johannes Vermeer]
-
A.
hasNearbyCemetery
Indicates that one entity is located close to, or in the immediate vicinity of, a cemetery associated with another entity.
-
B.
hasGravestone
Indicates that one entity possesses, is associated with, or is commemorated by a gravestone.
-
C.
buriedNear
chosen
Indicates that one entity is interred or buried in close physical proximity to another entity.
-
D.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
-
E.
hasGraveOrMemorialOf
Indicates that a location or object serves as the grave or memorial site dedicated to a particular person or 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b201d1508190a9d6abbfd04bdcae |
completed | April 19, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.