Triple
T37771559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kasuga Station |
E941559
|
entity |
| Predicate | hasStationCodeOnToeiOedoLine |
P95306
|
FINISHED |
| Object | E-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: E-07 | Statement: [Kasuga Station, hasStationCodeOnToeiOedoLine, E-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStationCodeOnToeiOedoLine Context triple: [Kasuga Station, hasStationCodeOnToeiOedoLine, E-07]
-
A.
ToeiSubwayStationNumber
chosen
Indicates the identification number assigned to a station within the Toei Subway system.
-
B.
TokyuStationNumber
Indicates that an entity is assigned a specific station number within the Tokyu railway network.
-
C.
adjacentStationOnToeiOedoLine
Indicates that one station is directly next to another station along the Toei Ōedo subway line, with no other stations in between.
-
D.
TokyoMetroStationNumber
Indicates that an entity is assigned a specific official station number within the Tokyo Metro railway network.
-
E.
hasAdjacentStationOnYurakuchoLine
Indicates that one station is directly next to another station along the Yurakucho Line.
- 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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0091ad8b8c8190b0f00a3358e59bc1 |
completed | May 10, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_6a008f2813ec81909a54c2dfa5c75dc7 |
completed | May 10, 2026, 1:59 p.m. |
Created at: May 3, 2026, 4:19 p.m.