Triple
T9029993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harris Controls Division |
E216143
|
entity |
| Predicate | DNP3Use |
P85774
|
FINISHED |
| Object | electric utility telemetry |
—
|
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: electric utility telemetry | Statement: [Harris Controls Division, DNP3Use, electric utility telemetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DNP3Use Context triple: [Harris Controls Division, DNP3Use, electric utility telemetry]
-
A.
deltaUse
Indicates a change in how something is used or the difference between two states of usage.
-
B.
usesDRS
Indicates that one entity employs or relies on a specific Decision Review System (DRS) for evaluation, verification, or decision-making purposes.
-
C.
definesUseOf
Indicates that one entity specifies or determines how another entity is to be used or applied.
-
D.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
E.
terminal3Use
Indicates that an entity makes use of or operates from terminal 3 (such as a specific terminal in a facility, station, or airport).
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a9e0aa881908886f453c51ecd0e |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f6dec4081909379bd57c02a5710 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:08 p.m.