Triple
T7928265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 868 |
E184121
|
entity |
| Predicate | networkLayerDependency |
P11823
|
FINISHED |
| Object | IP |
—
|
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 | Statement: [RFC 868, networkLayerDependency, IP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkLayerDependency Context triple: [RFC 868, networkLayerDependency, IP]
-
A.
networkLayerIndependence
Indicates that the relationship or action remains valid and unaffected regardless of the underlying network layer or transport mechanism used.
-
B.
linkLayer
Indicates a relationship where one entity is connected to another at the data link (Layer 2) level of a network stack, enabling direct frame-level communication between them.
-
C.
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.
-
D.
transportLayerFor
Indicates that one entity functions as the transport-layer protocol or mechanism used to carry or deliver another entity’s data.
-
E.
networkService
Indicates that one entity provides or participates in a network-based service or functionality for another entity or system.
- 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_69ca828fe7bc819090f52c88dcd72183 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3ac9ac4c819082cd2190fc3ce5a2 |
completed | March 31, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69cae9335f288190ba96781fd6576a2b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:07 p.m.