Triple
T28402890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomb of Vincent van Gogh |
E719436
|
entity |
| Predicate | hasNotableVisitors |
P10756
|
FINISHED |
| Object | art historians |
—
|
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: art historians | Statement: [Tomb of Vincent van Gogh, hasNotableVisitors, art historians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableVisitors Context triple: [Tomb of Vincent van Gogh, hasNotableVisitors, art historians]
-
A.
hasVisitorsFrom
Indicates that an entity receives or has received visitors originating from another specified entity or location.
-
B.
hasNotableGuest
chosen
Indicates that an entity has a guest who is distinguished, prominent, or otherwise noteworthy in some significant way.
-
C.
hasTargetVisitors
Indicates that something is intended or designed to be visited by a specific group of people as its primary audience or users.
-
D.
hasNotableHost
Indicates that an entity is associated with a host who is particularly prominent, famous, or otherwise noteworthy.
-
E.
hasVisitation
Indicates that one entity visits, or is allowed or scheduled to visit, another entity or location.
- 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_69ff2636e2bc8190bba91eff91431c6e |
completed | May 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69ff25c65be48190868480d94e1c4e89 |
completed | May 9, 2026, 12:17 p.m. |
Created at: April 28, 2026, 1:21 a.m.