Triple
T27401533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zoshigaya |
E691857
|
entity |
| Predicate | cemeteryNameDerivedFrom |
P162383
|
FINISHED |
| Object | Zoshigaya 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: Zoshigaya Cemetery | Statement: [Zoshigaya, cemeteryNameDerivedFrom, Zoshigaya Cemetery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cemeteryNameDerivedFrom Context triple: [Zoshigaya, cemeteryNameDerivedFrom, Zoshigaya Cemetery]
-
A.
cemeteryName
Indicates the name assigned to a cemetery associated with an entity.
-
B.
cemeteryMaintainedBy
Indicates that the upkeep, care, or management of a cemetery is performed or overseen by a specified agent or organization.
-
C.
associatedCemetery
Indicates that there is a relationship linking an entity (such as a person, event, or organization) to a specific cemetery with which it is connected.
-
D.
isCemeteryFor
Indicates that one entity serves as the burial ground designated for another entity, such as a community, group, or location.
-
E.
cemeteryKnownFor
Indicates that a cemetery is notable or recognized for a particular person, event, feature, or characteristic.
- 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_69ef5204f7048190bf226a129858fc5b |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62cd2ceb481908cd9fae52a542206 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f624c006788190a2f4d5015c96463f |
completed | May 2, 2026, 4:22 p.m. |
Created at: April 27, 2026, 12:29 p.m.