Triple
T30245710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Metro 16000 series |
E769046
|
entity |
| Predicate | primaryLineUsedOn |
P36093
|
FINISHED |
| Object | Tokyo Metro Chiyoda Line |
E214411
|
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: Tokyo Metro Chiyoda Line | Statement: [Tokyo Metro 16000 series, primaryLineUsedOn, Tokyo Metro Chiyoda Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLineUsedOn Context triple: [Tokyo Metro 16000 series, primaryLineUsedOn, Tokyo Metro Chiyoda Line]
-
A.
primaryTrunkLine
Indicates a relationship where one line functions as the main or principal trunk route among a set of connected lines.
-
B.
lineUses
Indicates that a particular line (such as a route, service, or connection) makes use of or is implemented using a specified resource, infrastructure, or element.
-
C.
lineUse
Indicates how a particular line (such as a route, track, or service line) is utilized or purposed within a system or network.
-
D.
alsoUsedOnLine
chosen
Indicates that something used in one context, medium, or location is additionally used on a specific line (such as a route, circuit, or sequence).
-
E.
secondaryLine
Indicates that something serves as a secondary or auxiliary line in relation to a primary or main line.
- 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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a01e993fec0819090cc397218515e88 |
completed | May 11, 2026, 2:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a81c5b0c2408190a4e755de41f5a02b |
completed | Aug. 16, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_6a01e57594188190a2354f48cf71b48c |
completed | May 11, 2026, 2:19 p.m. |
Created at: April 29, 2026, 7:39 p.m.