Triple
T18294114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frame Relay |
E438186
|
entity |
| Predicate | encapsulationDefinedIn |
P23699
|
FINISHED |
| Object | RFC 2427 |
—
|
NE NERFINISHED |
How this triple was built (3 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: RFC 2427 | Statement: [Frame Relay, encapsulationDefinedIn, RFC 2427]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2427 Context triple: [Frame Relay, encapsulationDefinedIn, RFC 2427]
-
A.
RFC 2487
RFC 2487 is an Internet standards document that originally defined the STARTTLS extension for securing SMTP connections with TLS, later superseded by RFC 3207.
-
B.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
-
C.
RFC 2447
RFC 2447 is an Internet standards document that originally specified how to integrate iCalendar-based scheduling with email using the iMIP protocol.
-
D.
RFC 3727
RFC 3727 is an Internet Engineering Task Force (IETF) document that defined earlier specifications for LDAP-related schema or matching rules, later superseded by RFC 4517.
-
E.
RFC 2279
RFC 2279 is an older Internet standard that originally defined UTF-8 as a transformation format for Unicode, later superseded by RFC 3629.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2427 Target entity description: RFC 2427 is an IETF standard that specifies how to encapsulate multiple network layer protocols over Frame Relay networks.
-
A.
RFC 2487
RFC 2487 is an Internet standards document that originally defined the STARTTLS extension for securing SMTP connections with TLS, later superseded by RFC 3207.
-
B.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
-
C.
RFC 2447
RFC 2447 is an Internet standards document that originally specified how to integrate iCalendar-based scheduling with email using the iMIP protocol.
-
D.
RFC 3727
RFC 3727 is an Internet Engineering Task Force (IETF) document that defined earlier specifications for LDAP-related schema or matching rules, later superseded by RFC 4517.
-
E.
RFC 2279
RFC 2279 is an older Internet standard that originally defined UTF-8 as a transformation format for Unicode, later superseded by RFC 3629.
- F. None of above. chosen
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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5010205bc8190a32fe731ead3d988 |
completed | April 19, 2026, 4:21 p.m. |
Created at: April 10, 2026, 10:35 a.m.