Triple
T24760333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kawanishi-Ikeda Station |
E619417
|
entity |
| Predicate | privatizationDateToJRWest |
P23781
|
FINISHED |
| Object | 1987-04-01 |
—
|
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: 1987-04-01 | Statement: [Kawanishi-Ikeda Station, privatizationDateToJRWest, 1987-04-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: privatizationDateToJRWest Context triple: [Kawanishi-Ikeda Station, privatizationDateToJRWest, 1987-04-01]
-
A.
privatizedOn
chosen
Indicates the date or point in time when an entity transitioned from public or state ownership/control to private ownership/control.
-
B.
underlyingCompanyPrivatizationYear
Indicates the year in which the underlying company was privatized.
-
C.
TokyoMetroSectionOpeningDate
Indicates the calendar date on which a specific section of the Tokyo Metro railway network was officially opened for service.
-
D.
railPrivatisationContext
Indicates the relationship in which an event, statement, or policy is situated within the broader circumstances or framework of rail privatisation.
-
E.
ShinkansenServiceStarted
Indicates that a Shinkansen (high-speed rail) service has commenced operation on a particular route or section.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:27 a.m.