Triple
T29752764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 894 |
E752944
|
entity |
| Predicate | usesEtherType |
P168781
|
FINISHED |
| Object | 0x0800 |
—
|
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: 0x0800 | Statement: [RFC 894, usesEtherType, 0x0800]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesEtherType Context triple: [RFC 894, usesEtherType, 0x0800]
-
A.
energyEfficientEthernetStandard
Indicates that the subject conforms to or supports the Energy-Efficient Ethernet (EEE) standard for reducing power consumption in Ethernet networking.
-
B.
usesIPProtocol
Indicates that one entity communicates or operates using a specific IP (Internet Protocol) version or protocol.
-
C.
supportsVLANTagging
Indicates that one entity provides the capability for another entity or interface to handle and process VLAN-tagged network traffic.
-
D.
networkInterfaceType
Indicates the specific kind or category of network interface used to connect entities within a network.
-
E.
typicalMTU
Indicates that one entity is the typical or most common member type or unit associated with another 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67805551c81909e016ae9e3031076 |
completed | May 2, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676f73c3481909f01fa69851b7298 |
completed | May 2, 2026, 10:13 p.m. |
Created at: April 28, 2026, 7:54 p.m.