Triple
T35804235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magome-juku |
E1035063
|
entity |
| Predicate | formerPostStationNumber |
P202327
|
FINISHED |
| Object | 43 |
—
|
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: 43 | Statement: [Magome-juku, formerPostStationNumber, 43]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerPostStationNumber Context triple: [Magome-juku, formerPostStationNumber, 43]
-
A.
formerStationCode
Indicates that an entity previously had a specific station code that is no longer in current use.
-
B.
formerStationNameFor
Indicates that one station name was previously used as the official name for another station.
-
C.
formerStationOnLine
Indicates that a station previously belonged to or operated on a particular transit line but is no longer in service on that line.
-
D.
formerTerminalStation
Indicates that a location once served as the end point (terminus) of a transportation line or route but no longer holds that status.
-
E.
formerRouteNumber
Indicates that an entity previously had a specific route number before being renumbered, discontinued, or otherwise changed.
- 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a007241df8081909dbad651fda82aa7 |
completed | May 10, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_6a0071e77ed081908cd618da8977d878 |
completed | May 10, 2026, 11:54 a.m. |
| PDg | Predicate description generation | batch_6a007240adac819087ab65e9733c384f |
completed | May 10, 2026, 11:55 a.m. |
Created at: May 3, 2026, 4:06 p.m.