Triple
T2347218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tama Cemetery |
E45157
|
entity |
| Predicate | isCemeteryFor |
P38888
|
FINISHED |
| Object | residents of Tokyo |
—
|
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: residents of Tokyo | Statement: [Tama Cemetery, isCemeteryFor, residents of Tokyo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCemeteryFor Context triple: [Tama Cemetery, isCemeteryFor, residents of Tokyo]
-
A.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
-
B.
isPublicCemetery
Indicates that a cemetery is designated, maintained, or recognized as a public burial ground accessible for general community use.
-
C.
locatedInCemetery
Indicates that one entity is situated within the grounds or area of a cemetery.
-
D.
cemeteryType
Indicates the specific kind or classification of a cemetery associated with an entity.
-
E.
hasCemeteryType
Indicates that a cemetery is classified as belonging to a specific type or category of cemetery.
- 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_69a88917935081909b755dbf38e81024 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abcade3c808190ab3803538ccbe620 |
completed | March 7, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69abc59616a8819099711834e6f1ccd6 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abcadd2a0c8190b6973d390e98bd66 |
completed | March 7, 2026, 6:51 a.m. |
Created at: March 4, 2026, 7:52 p.m.