Triple
T20139277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Link Aggregation Control Protocol |
E491114
|
entity |
| Predicate | notProvide |
P131596
|
FINISHED |
| Object | per-flow bandwidth guarantee |
—
|
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: per-flow bandwidth guarantee | Statement: [Link Aggregation Control Protocol, notProvide, per-flow bandwidth guarantee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notProvide Context triple: [Link Aggregation Control Protocol, notProvide, per-flow bandwidth guarantee]
-
A.
doesNotProvideFor
chosen
Indicates that one entity fails or is not responsible for supplying support, resources, or necessary provisions to another entity.
-
B.
notUsedAt
Indicates that a particular entity is not utilized, applied, or active at a specified location, time, or context.
-
C.
notAbout
Indicates that a given entity, statement, or resource does not concern, reference, or pertain to another specified entity or topic.
-
D.
notGuaranteed
Indicates that the specified outcome, condition, or obligation is not assured to occur or be fulfilled.
-
E.
notDescribedAs
Indicates that an entity is explicitly not characterized, labeled, or referred to using a particular description or term.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667698a188190869c18b925dba2ed |
completed | April 20, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:32 p.m.