Triple
T20399921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IP over InfiniBand |
E500303
|
entity |
| Predicate | definedIn |
P775
|
FINISHED |
| Object | IETF RFC 4393 |
—
|
NE NERFINISHED |
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: IETF RFC 4393 | Statement: [IP over InfiniBand, definedIn, IETF RFC 4393]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IETF RFC 4393 Context triple: [IP over InfiniBand, definedIn, IETF RFC 4393]
-
A.
IETF RFC 4392
chosen
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.
-
B.
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.
-
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 4633
RFC 4633 is an Internet Engineering Task Force (IETF) standard that updates and refines the Classless Inter-Domain Routing (CIDR) architecture for IP addressing and routing.
-
E.
RFC 4330
RFC 4330 is an Internet Engineering Task Force (IETF) specification that defines a simple network time protocol (SNTP) for synchronizing computer clocks over IP networks.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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. |
Created at: April 16, 2026, 11:29 a.m.