Triple
T34565905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grover's Corners |
E887480
|
entity |
| Predicate | hasCemeteryName |
P107125
|
FINISHED |
| Object | Gibbs Memorial Cemetery |
—
|
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: Gibbs Memorial Cemetery | Statement: [Grover's Corners, hasCemeteryName, Gibbs Memorial Cemetery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCemeteryName Context triple: [Grover's Corners, hasCemeteryName, Gibbs Memorial Cemetery]
-
A.
cemeteryName
chosen
Indicates the name assigned to a cemetery associated with an entity.
-
B.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
-
C.
isCemeteryFor
Indicates that one entity serves as the burial ground designated for another entity, such as a community, group, or location.
-
D.
cemeteryNameDerivedFrom
Indicates that the name of a cemetery is derived from, or based on, another specified entity or source.
-
E.
hasNearbyCemetery
Indicates that one entity is located close to, or in the immediate vicinity of, a cemetery associated with 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_69f349d0c4d881908dd0950f5eb9ec0a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 1, 2026, 2:02 a.m.