Triple
T20399919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IP over InfiniBand |
E500303
|
entity |
| Predicate | definedIn |
P775
|
FINISHED |
| Object |
IETF RFC 4392
IETF RFC 4392 is a standards-track document from the Internet Engineering Task Force that specifies how to encapsulate and transport IP traffic over InfiniBand networks.
|
E1429941
|
NE FINISHED |
How this triple was built (4 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: IETF RFC 4392 | Statement: [IP over InfiniBand, definedIn, IETF RFC 4392]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IETF RFC 4392 Context triple: [IP over InfiniBand, definedIn, IETF RFC 4392]
-
A.
IETF RFC 4391
IETF RFC 4391 is a standards-track document from the Internet Engineering Task Force that specifies how the Internet Protocol (IP) operates over InfiniBand networks.
-
B.
RFC 3492
RFC 3492 is the Internet standard document that defines Punycode, an encoding method used to represent Unicode characters in domain names using only ASCII characters.
-
C.
RFC 4395
RFC 4395 was an IETF document that originally defined the procedures and guidelines for registering new URI schemes before being superseded by RFC 7320.
-
D.
RFC 3490
RFC 3490 is an Internet standard that defines Internationalized Domain Names in Applications (IDNA), enabling the use of non-ASCII characters in domain names.
-
E.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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: IETF RFC 4392 Triple: [IP over InfiniBand, definedIn, IETF RFC 4392]
Generated description
IETF RFC 4392 is a standards-track document from the Internet Engineering Task Force that specifies how to encapsulate and transport IP traffic over InfiniBand networks.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: IETF RFC 4392 Target entity description: IETF RFC 4392 is a standards-track document from the Internet Engineering Task Force that specifies how to encapsulate and transport IP traffic over InfiniBand networks.
-
A.
IETF RFC 4391
IETF RFC 4391 is a standards-track document from the Internet Engineering Task Force that specifies how the Internet Protocol (IP) operates over InfiniBand networks.
-
B.
RFC 3492
RFC 3492 is the Internet standard document that defines Punycode, an encoding method used to represent Unicode characters in domain names using only ASCII characters.
-
C.
RFC 4395
RFC 4395 was an IETF document that originally defined the procedures and guidelines for registering new URI schemes before being superseded by RFC 7320.
-
D.
RFC 3490
RFC 3490 is an Internet standard that defines Internationalized Domain Names in Applications (IDNA), enabling the use of non-ASCII characters in domain names.
-
E.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
- F. None of above. chosen
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_69e0b4a81bec8190b69adfdc1336a015 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6798db79c819085e3a2526538726f |
completed | April 20, 2026, 7:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a087b17960081908497556574011fd3 |
completed | May 16, 2026, 2:11 p.m. |
| NEDg | Description generation | batch_6a088014c30c8190937586dc3f23862e |
completed | May 16, 2026, 2:32 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a08810e37c08190bd7e8b584204064c |
completed | May 16, 2026, 2:37 p.m. |
Created at: April 16, 2026, 11:29 a.m.