Triple
T4653340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mingorrubio Cemetery |
E102347
|
entity |
| Predicate | publicCemetery |
P28157
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mingorrubio Cemetery, publicCemetery, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicCemetery Context triple: [Mingorrubio Cemetery, publicCemetery, yes]
-
A.
isPublicCemetery
chosen
Indicates that a cemetery is designated, maintained, or recognized as a public burial ground accessible for general community use.
-
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.
hasNearbyCemetery
Indicates that one entity is located close to, or in the immediate vicinity of, a cemetery associated with another entity.
-
E.
cemeterySection
Indicates that one entity is a specific section, area, or subdivision within a cemetery associated with the other 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_69bd43d71a308190afea7280841b0de8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd6314883481908f085a7af497b0d8 |
completed | March 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69bd62126b0c81909ba3f21b21e30d54 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:14 p.m.