Triple
T21376336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hankyu Imazu Line |
E527214
|
entity |
| Predicate | usesElectricMultipleUnits |
P144017
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hankyu Imazu Line, usesElectricMultipleUnits, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesElectricMultipleUnits Context triple: [Hankyu Imazu Line, usesElectricMultipleUnits, yes]
-
A.
electrificationUsedBy
Indicates that a particular electrification system, method, or technology is employed or utilized by a given entity.
-
B.
electrificationCompatibility
Indicates whether one entity can be effectively and safely powered, charged, or operated using the electrical system, standards, or infrastructure associated with another entity.
-
C.
isElectrically
Indicates that one entity has an electrical property, connection, or interaction in relation to another entity.
-
D.
hasElectricCarts
Indicates that an entity provides or uses electric carts, typically for transportation or logistical purposes.
-
E.
electrificationUsedFor
Indicates that electrification is employed as a means or method to achieve, enable, or support a particular function, process, or purpose.
- F. None of above. chosen
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_69e0b51e80808190ba5cb05667af02a9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69ee62c9494081909efa74e189454dc6 |
completed | April 26, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69e61b3e47f881908fb2aac9bd2bfb58 |
completed | April 20, 2026, 12:25 p.m. |
Created at: April 16, 2026, 5:11 p.m.