Triple
T21715848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 国府津駅 |
E536025
|
entity |
| Predicate | 開業年代区分 |
P48685
|
FINISHED |
| Object | 19世紀に開業した日本の鉄道駅 |
—
|
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: 19世紀に開業した日本の鉄道駅 | Statement: [国府津駅, 開業年代区分, 19世紀に開業した日本の鉄道駅]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 開業年代区分 Context triple: [国府津駅, 開業年代区分, 19世紀に開業した日本の鉄道駅]
-
A.
officialOpeningYear
Indicates the calendar year in which something was formally opened or inaugurated for official use.
-
B.
structureOpeningYear
Indicates the calendar year in which a structure was first opened for use or public access.
-
C.
placeEstablished
Indicates that an entity was founded, created, or formally established at a particular place or location.
-
D.
eraOfEstablishment
chosen
Indicates the time period or historical era during which an entity was founded or established.
-
E.
approximateOpeningYear
Indicates the estimated or roughly determined year in which something (such as a facility, venue, or organization) began operating or opened.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd96ab4c88190b76f4a6b7c855039 |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:47 p.m.