Triple
T10158072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7622 |
E233820
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RFC 6120 |
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: RFC 6120 | Statement: [RFC 7622, relatedTo, RFC 6120]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 6120 Context triple: [RFC 7622, relatedTo, RFC 6120]
-
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 6122
RFC 6122 is an Internet standard that specifies the format and handling of XMPP (Jabber) addresses, defining how identifiers are structured and compared in the Extensible Messaging and Presence Protocol.
-
C.
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).
-
D.
RFC 6186
RFC 6186 is an Internet Engineering Task Force (IETF) standard that originally specified how to use DNS SRV records to locate email submission and access services for a given domain.
-
E.
RFC 5849
RFC 5849 is the Internet standard that originally defined the OAuth 1.0 protocol for secure delegated authorization before being superseded by OAuth 2.0 in RFC 6749.
- 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_69d32ac043f08190ba7f526d226d3c8c |
completed | April 6, 2026, 3:38 a.m. |
Created at: March 30, 2026, 9:09 p.m.