Triple
T21685333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 多磨霊園 |
E535214
|
entity |
| Predicate | 開設日 |
P30383
|
FINISHED |
| Object | 1923年 |
—
|
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: 1923年 | Statement: [多磨霊園, 開設日, 1923年]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 開設日 Context triple: [多磨霊園, 開設日, 1923年]
-
A.
officialOpeningDate
Indicates the calendar date on which something is formally inaugurated or officially opened for use or operation.
-
B.
openingDay
Indicates the specific day on which something, typically an event, season, or venue, officially begins or first opens to the public.
-
C.
openedAt
chosen
Indicates that an entity began operating, became accessible, or was first made available at a specific time or date.
-
D.
establishedAt
Indicates the specific time or date at which something (such as an organization, system, or entity) was founded or brought into existence.
-
E.
firstLineOpeningDate
Indicates the date on which the first line in a system, network, or service was officially opened or began operation.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96ca668481909f53853c7a8ea811 |
completed | April 27, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:44 p.m.