Triple
T9029999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harris Controls Division |
E216143
|
entity |
| Predicate | DNP3Domain |
P80109
|
FINISHED |
| Object | electric power transmission and distribution |
—
|
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 power transmission and distribution | Statement: [Harris Controls Division, DNP3Domain, electric power transmission and distribution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DNP3Domain Context triple: [Harris Controls Division, DNP3Domain, electric power transmission and distribution]
-
A.
controlDomain
Indicates that one entity has authority over, manages, or regulates the scope, behavior, or operations of another entity or system.
-
B.
transportDomain
Indicates a relationship where an entity operates or functions within the domain or context of transportation activities or systems.
-
C.
networkProtocolDomain
chosen
Indicates the network protocol or protocol family within which a given communication, service, or interaction operates.
-
D.
routingDomainType
Indicates the classification or category of routing domain associated with a given routing configuration or relationship.
-
E.
hasCommunicationDomain
Indicates that one entity operates, functions, or is relevant within a specified communication-related domain or area.
- 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_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. |
Created at: March 30, 2026, 7:08 p.m.