Triple
T37149346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5047 |
E920321
|
entity |
| Predicate | defines |
P264
|
FINISHED |
| Object |
RDMA over reliable transports
RDMA over reliable transports is a networking approach that enables remote direct memory access operations across a network using underlying transport protocols that provide reliable, ordered delivery of data.
|
E2221375
|
NE 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: RDMA over reliable transports | Statement: [RFC 5047, defines, RDMA over reliable transports]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: RDMA over reliable transports Triple: [RFC 5047, defines, RDMA over reliable transports]
Generated description
RDMA over reliable transports is a networking approach that enables remote direct memory access operations across a network using underlying transport protocols that provide reliable, ordered delivery of data.
Provenance (5 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb308bfe4c81909e4f6f2737246456 |
completed | May 6, 2026, 12:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a405118615081908b4beacfc191b4f6 |
completed | June 27, 2026, 10:39 p.m. |
| NEDg | Description generation | batch_6a405860921c8190ae3dab4fa7c68059 |
completed | June 27, 2026, 11:10 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a4058b1347c819089853982dc595947 |
completed | June 27, 2026, 11:11 p.m. |
Created at: May 3, 2026, 4:15 p.m.