Triple
T7836023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cisco ACI |
E181692
|
entity |
| Predicate | controlPlane |
P66322
|
FINISHED |
| Object | APIC policy 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: APIC policy distribution | Statement: [Cisco ACI, controlPlane, APIC policy distribution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlPlane Context triple: [Cisco ACI, controlPlane, APIC policy distribution]
-
A.
controlPlaneEntity
chosen
Indicates that one entity functions as part of, or in association with, a system’s control plane, managing or coordinating control-related operations for that system.
-
B.
controlDomain
Indicates that one entity has authority over, manages, or regulates the scope, behavior, or operations of another entity or system.
-
C.
controlGroup
Indicates that one entity functions as the control group against which another condition, treatment, or experimental group is compared.
-
D.
controlSegment
Indicates that one entity governs, directs, or regulates a specific segment or portion of another entity or system.
-
E.
controlLayout
Indicates that one entity determines or manages the spatial or structural arrangement of another entity.
- 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_69ca8284a25c8190a1a20afad30da792 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb064cb7e081909e88419863d94dfe |
completed | March 30, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69cae91e98988190abd4ece75932c589 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:46 p.m.