Triple
T17733411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kokkai-gijidō-mae Station |
E442644
|
entity |
| Predicate | chiyodaLineStationCode |
P95305
|
FINISHED |
| Object | C-07 |
—
|
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: C-07 | Statement: [Kokkai-gijidō-mae Station, chiyodaLineStationCode, C-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chiyodaLineStationCode Context triple: [Kokkai-gijidō-mae Station, chiyodaLineStationCode, C-07]
-
A.
TokyoMetroStationNumber
chosen
Indicates that an entity is assigned a specific official station number within the Tokyo Metro railway network.
-
B.
TokyuStationNumber
Indicates that an entity is assigned a specific station number within the Tokyu railway network.
-
C.
ToeiSubwayStationNumber
Indicates the identification number assigned to a station within the Toei Subway system.
-
D.
adjacentToStationOnChiyodaLine
Indicates that one entity is directly next to or neighboring a station located on the Chiyoda railway line.
-
E.
TokyoMetroSection
Indicates a relationship where a specific segment or portion of the Tokyo Metro railway network is identified as a distinct section within the system.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e478e86f188190a5dd7fb32fd04c7b |
completed | April 19, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:08 a.m.