Triple
T245118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.1AE |
E5019
|
entity |
| Predicate | isIndependentOf |
P243
|
FINISHED |
| Object | upper-layer protocols |
—
|
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: upper-layer protocols | Statement: [IEEE 802.1AE, isIndependentOf, upper-layer protocols]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIndependentOf Context triple: [IEEE 802.1AE, isIndependentOf, upper-layer protocols]
-
A.
independenceFrom
chosen
Indicates that one entity is not controlled, governed, or significantly influenced by another entity.
-
B.
typeOfIndependence
Indicates the specific nature or category of independence that applies to an entity or relationship.
-
C.
hasIndependentCity
Indicates that a larger administrative region or entity contains a city that is administratively independent from the surrounding local jurisdictions.
-
D.
doesNotCoupleTo
Indicates that one entity does not form a functional or physical coupling or interaction with another entity.
-
E.
independenceRecognized
Indicates that one entity formally acknowledges another entity’s status as independent and self-governing.
- 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.