Triple
T16747246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EAP over LAN |
E406987
|
entity |
| Predicate | roleIn8021X |
P57746
|
FINISHED |
| Object | carries EAP between supplicant and authenticator |
—
|
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: carries EAP between supplicant and authenticator | Statement: [EAP over LAN, roleIn8021X, carries EAP between supplicant and authenticator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleIn8021X Context triple: [EAP over LAN, roleIn8021X, carries EAP between supplicant and authenticator]
-
A.
roleInGateway
Indicates that an entity holds a specific function or responsibility within a particular gateway system or process.
-
B.
roleInProtocolStack
chosen
Indicates the specific function or position an entity occupies within a layered communication or protocol stack.
-
C.
ClientRole
Indicates that an entity participates in a relationship or interaction specifically in the capacity of a client.
-
D.
roleIn3GPP
Indicates that an entity holds a specific role or function within the context of 3GPP (Third Generation Partnership Project) standards or activities.
-
E.
campusNetworkRole
Indicates the specific function or responsibility an entity has within a campus network environment.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa2311748190a17416de577ad159 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.