Triple
T29356672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ekō-in Temple |
E744461
|
entity |
| Predicate | hasGravesOrCenotaphsFor |
P78565
|
FINISHED |
| Object | victims of fires |
—
|
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: victims of fires | Statement: [Ekō-in Temple, hasGravesOrCenotaphsFor, victims of fires]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGravesOrCenotaphsFor Context triple: [Ekō-in Temple, hasGravesOrCenotaphsFor, victims of fires]
-
A.
hasGraveOrMemorialOf
chosen
Indicates that a location or object serves as the grave or memorial site dedicated to a particular person or entity.
-
B.
hasGravesOfCitizenship
Indicates that a place contains graves belonging to individuals of a specified citizenship.
-
C.
hasMassGraveOf
Indicates that a location or site contains a mass grave in which the referenced individuals or remains are buried.
-
D.
containsWarGravesOf
Indicates that a place or site includes burial locations or memorials for individuals who died in war.
-
E.
hasWarGravesMaintainedBy
Indicates that one entity contains war graves whose upkeep and preservation are carried out by 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 28, 2026, 2:13 p.m.