Triple
T7835886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EVPN |
E181689
|
entity |
| Predicate | dataPlaneType |
P79285
|
FINISHED |
| Object | IP or MPLS underlay |
—
|
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: IP or MPLS underlay | Statement: [EVPN, dataPlaneType, IP or MPLS underlay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataPlaneType Context triple: [EVPN, dataPlaneType, IP or MPLS underlay]
-
A.
dataBusType
Indicates the type or category of data bus used to transfer data between components or systems.
-
B.
dataTypes
Indicates that one entity specifies or defines the kinds or formats of data that are valid or expected for another entity.
-
C.
networkType
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
D.
interconnectionType
Indicates the specific kind or nature of relationship that links two or more entities together.
-
E.
tunnelType
Indicates the specific kind or classification of a tunnel associated with an entity.
- F. None of above. chosen
Provenance (4 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_69ca8284a25c8190a1a20afad30da792 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb064cb7e081909e88419863d94dfe |
completed | March 30, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69cae91e98988190abd4ece75932c589 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7855a3c81908b9318f7186fc0c0 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:46 p.m.