Triple
T7835944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cisco FabricPath |
E181691
|
entity |
| Predicate | usesControlPlane |
P66322
|
FINISHED |
| Object | routing-like control plane |
—
|
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: routing-like control plane | Statement: [Cisco FabricPath, usesControlPlane, routing-like control plane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesControlPlane Context triple: [Cisco FabricPath, usesControlPlane, routing-like control plane]
-
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.
usedToControl
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
-
C.
usedControl
Indicates that one entity exercised or applied a control mechanism or method over another entity or process.
-
D.
usesController
Indicates that one entity operates, manages, or interacts with another entity through a controller component or mechanism.
-
E.
hasControlTower
Indicates that one entity possesses, hosts, or is equipped with a control tower that manages or oversees its operations.
- 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.