Triple
T30245750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Metro 16000 series |
E769046
|
entity |
| Predicate | hasPantographType |
P111725
|
FINISHED |
| Object | single-arm pantograph |
—
|
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: single-arm pantograph | Statement: [Tokyo Metro 16000 series, hasPantographType, single-arm pantograph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPantographType Context triple: [Tokyo Metro 16000 series, hasPantographType, single-arm pantograph]
-
A.
hasPantograph
chosen
Indicates that one entity is equipped with or possesses a pantograph used for drawing power or making contact with an overhead system.
-
B.
hasLiftType
Indicates the specific type or category of lift associated with an entity.
-
C.
pantographModification
Indicates a modification or alteration made to a pantograph mechanism in relation to another entity or system.
-
D.
hasRetractablePitch
Indicates that an entity (typically a stadium or venue) possesses a playing surface or pitch that can be mechanically extended or withdrawn as needed.
-
E.
hasRollingStockFeature
Indicates that a piece of rolling stock possesses a specific feature, characteristic, or equipment.
- 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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: April 29, 2026, 7:39 p.m.