Triple
T37291160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MicroLogix |
E925667
|
entity |
| Predicate | powerSupplyOption |
P44389
|
FINISHED |
| Object | 120/240 VAC |
—
|
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: 120/240 VAC | Statement: [MicroLogix, powerSupplyOption, 120/240 VAC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerSupplyOption Context triple: [MicroLogix, powerSupplyOption, 120/240 VAC]
-
A.
powerSupplyCapability
Indicates the ability of one entity to provide electrical power to another entity or system.
-
B.
powerSupplyInterface
Indicates a relationship where one entity provides or connects an electrical power source to another entity through a defined interface.
-
C.
powerSupplyWattage
Indicates the amount of electrical power, measured in watts, that a power supply can deliver.
-
D.
hasPowerSupplyType
chosen
Indicates that an entity is associated with a specific type or category of power supply it uses or requires.
-
E.
powerSupplyLocation
Indicates the physical place or component where an entity’s electrical power is provided or connected.
- 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_69f76eb0f86c819098dee07393e69ec3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: May 3, 2026, 4:16 p.m.