Triple
T13153464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.1Qbb |
E312522
|
entity |
| Predicate | typeOfFlowControl |
P3686
|
FINISHED |
| Object | priority-based |
—
|
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: priority-based | Statement: [IEEE 802.1Qbb, typeOfFlowControl, priority-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfFlowControl Context triple: [IEEE 802.1Qbb, typeOfFlowControl, priority-based]
-
A.
typeOfControl
Indicates the specific manner or mechanism by which one entity exercises control or influence over another.
-
B.
hasFlowType
Indicates the type or category of flow associated with or exhibited by an entity.
-
C.
controlStructure
Indicates a relationship where one entity governs, regulates, or directs the behavior, operation, or flow of another entity or process.
-
D.
typeOfControlSet
Indicates that one control or set of controls is defined, categorized, or governed as a specific type within a broader control framework or classification system.
-
E.
flowControl
chosen
Indicates a relationship where one entity regulates, directs, or manages the rate or sequence of another entity’s operations or movement.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:11 p.m.