Triple
T38607163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo electric power grid |
E934372
|
entity |
| Predicate | distributionVoltageToConsumers |
P34711
|
FINISHED |
| Object | 100 V |
—
|
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: 100 V | Statement: [Tokyo electric power grid, distributionVoltageToConsumers, 100 V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distributionVoltageToConsumers Context triple: [Tokyo electric power grid, distributionVoltageToConsumers, 100 V]
-
A.
gridVoltageLevel
chosen
Indicates the electrical voltage level at which a power grid or network segment operates.
-
B.
usesElectricityVoltage
Indicates that one entity operates using or is characterized by a specified level of electrical voltage supplied by another entity or source.
-
C.
electricityMarketedBy
Indicates that one entity is responsible for marketing, promoting, or selling electricity provided by another entity.
-
D.
electrificationServedBy
Indicates that the electrification of a system, area, or infrastructure is provided, supported, or enabled by a specified source, service, or entity.
-
E.
overheadLineVoltage
Indicates the voltage level carried by an overhead power line in the relationship.
- 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_69f76eccd6d081909ccce171011739a1 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.