Triple
T245094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.1AE |
E5019
|
entity |
| Predicate | subLayer |
P5995
|
FINISHED |
| Object | MAC sublayer |
—
|
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: MAC sublayer | Statement: [IEEE 802.1AE, subLayer, MAC sublayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subLayer Context triple: [IEEE 802.1AE, subLayer, MAC sublayer]
-
A.
subLayerInDataLinkLayer
chosen
Indicates that one protocol or component functions as a subordinate or encapsulated sublayer within another protocol or component in the data link layer of a network stack.
-
B.
subunitType
Indicates that one entity is a specific kind or classification of subunit within the structure or composition of another entity.
-
C.
subtitle
Indicates that one work serves as a secondary or explanatory title to another, typically appearing beneath the main title.
-
D.
formerSubunit
Indicates that one entity was previously a subunit or subordinate part of another entity, but no longer holds that status.
-
E.
subordinateTo
Indicates that one entity holds a lower rank, status, or authority and is subject to the control, direction, or oversight 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d10ac248190a98dedabf5358668 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b63b0bc8190864d7324d339fb48 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.