Triple
T19524765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trumpan |
E488491
|
entity |
| Predicate | cemeteryStatus |
P2742
|
FINISHED |
| Object | historic burial ground |
—
|
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: historic burial ground | Statement: [Trumpan, cemeteryStatus, historic burial ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cemeteryStatus Context triple: [Trumpan, cemeteryStatus, historic burial ground]
-
A.
burialStatus
Indicates the state or condition of whether and how an entity has been buried.
-
B.
isCemeteryFor
Indicates that one entity serves as the burial ground designated for another entity, such as a community, group, or location.
-
C.
cemeteryType
chosen
Indicates the specific kind or classification of a cemetery associated with an entity.
-
D.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
-
E.
cemeteryCapacitySupported
Indicates that an entity provides or supports the necessary capacity (such as space or resources) for a cemetery to operate or accommodate burials.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63639cfc08190894ac67f7d861a25 |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.