Triple
T32239046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Intercity Railway Company |
E823556
|
entity |
| Predicate | primaryServiceCorridor |
P46518
|
FINISHED |
| Object | central Tokyo – Tsukuba |
E1478367
|
NE 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: central Tokyo – Tsukuba | Statement: [Metropolitan Intercity Railway Company, primaryServiceCorridor, central Tokyo – Tsukuba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryServiceCorridor Context triple: [Metropolitan Intercity Railway Company, primaryServiceCorridor, central Tokyo – Tsukuba]
-
A.
primaryCorridorServed
chosen
Indicates that a corridor is the main route or pathway served by a given service, facility, or entity.
-
B.
primaryService
Indicates that one entity serves as the main or principal service provided or used in relation to another entity.
-
C.
primaryRouteThrough
Indicates that one location or path serves as the main or most significant route passing through another location or area.
-
D.
primaryRouteOf
Indicates that one route is the main or most important pathway used for reaching or connecting to a particular destination or entity.
-
E.
primaryRoute
Indicates that one route is designated as the main or preferred path among possible alternatives between locations.
- F. None of above.
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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f3bb19d6c8190b2d978351350086e |
completed | June 14, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:39 a.m.