Triple
T10157993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6120 |
E233818
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | RFC6120 |
E233818
|
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: RFC6120 | Statement: [RFC 6120, hasAbbreviation, RFC6120]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC6120 Context triple: [RFC 6120, hasAbbreviation, RFC6120]
-
A.
RFC 6120
chosen
RFC 6120 is an IETF standard that defines the core XML streaming and authentication framework for the Extensible Messaging and Presence Protocol (XMPP).
-
B.
RFC 6121
RFC 6121 is an IETF standard that defines the core instant messaging and presence functionality for the Extensible Messaging and Presence Protocol (XMPP).
-
C.
RFC 5061
RFC 5061 is an Internet Engineering Task Force (IETF) specification that extends and enhances the Stream Control Transmission Protocol (SCTP), particularly for dynamic address reconfiguration and improved transport flexibility.
-
D.
RFC 6410
RFC 6410 is an Internet Engineering Task Force (IETF) document that streamlines and updates the process for advancing technical specifications to Internet Standard status within the Internet Standards Process.
-
E.
RFC 6062
RFC 6062 is an IETF specification that extends the TURN protocol to support TCP relaying for applications operating across NATs and firewalls.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec5507f08190b47f797bacd5640c |
completed | April 2, 2026, 4:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d300acae608190891d8f55c3d5102b |
completed | April 6, 2026, 12:39 a.m. |
Created at: March 30, 2026, 9:09 p.m.