Triple
T23067856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joban Line (local services) |
E575100
|
entity |
| Predicate | openingDateOfLineSectionUsed |
P93179
|
FINISHED |
| Object | 1896 (Jōban Line historical opening) |
—
|
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: 1896 (Jōban Line historical opening) | Statement: [Joban Line (local services), openingDateOfLineSectionUsed, 1896 (Jōban Line historical opening)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingDateOfLineSectionUsed Context triple: [Joban Line (local services), openingDateOfLineSectionUsed, 1896 (Jōban Line historical opening)]
-
A.
railwaySectionOpeningDate
Indicates the date on which a specific section of a railway line was officially opened for operation.
-
B.
lineSectionOpeningDate
chosen
Indicates the date on which a specific section of a line (e.g., a route, track, or corridor) was officially opened for use.
-
C.
openingDateToRapidTransit
Indicates the date on which a rapid transit service or connection was opened or became operational.
-
D.
openingDateLineC
Indicates the calendar date on which entity C is opened, initiated, or begins operation.
-
E.
openingDateAsThroughLine
Indicates that the opening date is used as a continuous reference or organizing thread linking related events, records, or states over time.
- 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_69e245bd6e4c8190bb8942245b68cad5 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f189a5aa4081909b3f0dc92877323d |
completed | April 29, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:55 p.m.