Triple
T31004281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dudley Cemetery |
E790022
|
entity |
| Predicate | hasVisitationType |
P186471
|
FINISHED |
| Object | public access |
—
|
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: public access | Statement: [Dudley Cemetery, hasVisitationType, public access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisitationType Context triple: [Dudley Cemetery, hasVisitationType, public access]
-
A.
hasVisitorType
Indicates the type or category of visitor associated with an entity (e.g., guest, customer, tourist, patient).
-
B.
hasVisitation
Indicates that one entity visits, or is allowed or scheduled to visit, another entity or location.
-
C.
hasVisitationPurpose
Indicates that an entity’s visit to another entity or location is associated with a specific purpose or reason.
-
D.
hasAttendanceType
Indicates the specific category or mode of attendance associated with an event or participant (e.g., in-person, virtual, hybrid).
-
E.
hasTypeOfVisitorExperience
Indicates that an entity is associated with a particular category or kind of visitor experience it provides or involves.
- F. None of above. chosen
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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: April 29, 2026, 8:57 p.m.