Triple
T27572220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TRILL |
E696065
|
entity |
| Predicate | usesDataPlane |
P79285
|
FINISHED |
| Object | TRILL-encapsulated Ethernet |
—
|
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: TRILL-encapsulated Ethernet | Statement: [TRILL, usesDataPlane, TRILL-encapsulated Ethernet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDataPlane Context triple: [TRILL, usesDataPlane, TRILL-encapsulated Ethernet]
-
A.
dataPlaneType
chosen
Indicates the type or category of data plane through which data traffic or operations are carried out in a system or network.
-
B.
usesDataSystem
Indicates that one entity employs, accesses, or relies on a particular data system to perform its functions or operations.
-
C.
usesDataIn
Indicates that one entity relies on, accesses, or incorporates data from another entity in performing its function or operation.
-
D.
dataPlaneProxy
Indicates that one entity functions as a data-plane proxy that forwards or mediates traffic or data on behalf of another entity.
-
E.
usesDataLink
Indicates that one entity employs or relies on a data link connection to communicate with or transfer data to 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 1:43 p.m.