Triple
T35368657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warner, Oklahoma |
E1021706
|
entity |
| Predicate | electricalStandard |
P1048
|
FINISHED |
| Object | North American 120 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: North American 120 V | Statement: [Warner, Oklahoma, electricalStandard, North American 120 V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electricalStandard Context triple: [Warner, Oklahoma, electricalStandard, North American 120 V]
-
A.
usesElectricityStandard
chosen
Indicates that one entity operates according to, or is compatible with, the electricity supply standard defined or used by another entity.
-
B.
typeOfElectricity
Indicates that one entity specifies the particular kind or category of electricity associated with another entity.
-
C.
electricalPower
Indicates that one entity supplies, carries, or is associated with electrical power to or for another entity.
-
D.
electricalSystem
Indicates that one entity functions as, is part of, or is directly related to the electrical system of another entity.
-
E.
energyStandard
Indicates that an entity complies with, is classified by, or is governed according to a specified energy-related standard or efficiency criterion.
- 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_69f76df000488190ab7c97f565677055 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff49f888348190b9c55afa73b99e6a |
completed | May 9, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69ff49614ef88190ac70b034c55ad738 |
completed | May 9, 2026, 2:49 p.m. |
Created at: May 3, 2026, 4:03 p.m.