Triple
T26462625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rapid Spanning Tree Protocol |
E665676
|
entity |
| Predicate | configurationMode |
P158579
|
FINISHED |
| Object | per-VLAN implementation in many vendor products |
—
|
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-VLAN implementation in many vendor products | Statement: [Rapid Spanning Tree Protocol, configurationMode, per-VLAN implementation in many vendor products]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: configurationMode Context triple: [Rapid Spanning Tree Protocol, configurationMode, per-VLAN implementation in many vendor products]
-
A.
deploymentModeOfSystem
chosen
Indicates the specific deployment configuration or operational mode in which a system is set up or run.
-
B.
configurationVia
Indicates that one entity is set up, customized, or controlled through another entity serving as its configuration mechanism or source.
-
C.
configurationProtocol
Indicates the protocol or method used to configure or set up a system, device, or component.
-
D.
configurationLevel
Indicates the degree or tier of settings or parameters applied to configure something within a system or context.
-
E.
configurationFeatures
Indicates the specific options or characteristics that are enabled or defined within a particular configuration.
- 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 12:13 a.m.