Triple
T34360830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1662 |
E881867
|
entity |
| Predicate | networkProtocolLayer |
P11823
|
FINISHED |
| Object | Layer 2 |
—
|
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: Layer 2 | Statement: [RFC 1662, networkProtocolLayer, Layer 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkProtocolLayer Context triple: [RFC 1662, networkProtocolLayer, Layer 2]
-
A.
protocolLayer
chosen
Indicates a relationship where a communication protocol operates at, or is associated with, a specific layer in a protocol stack or network architecture.
-
B.
networkLayerSupport
Indicates that one entity provides or is compatible with the network-layer functionality or protocols required by another entity.
-
C.
networkLayerIndependence
Indicates that the relationship or action remains valid and unaffected regardless of the underlying network layer or transport mechanism used.
-
D.
applicationLayerProtocol
Indicates that one entity uses, implements, or is associated with a specific application-layer communication protocol in a networked interaction.
-
E.
networkProtocolDomain
Indicates the network protocol or protocol family within which a given communication, service, or interaction operates.
- 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_69f349be5c9c81908dc726ae1f4c68f2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: May 1, 2026, 1:58 a.m.