Triple
T10157978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6120 |
E233818
|
entity |
| Predicate | definesTerm |
P773
|
FINISHED |
| Object | XMPP stream |
E42571
|
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: XMPP stream | Statement: [RFC 6120, definesTerm, XMPP stream]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: XMPP stream Context triple: [RFC 6120, definesTerm, XMPP stream]
-
A.
XMPP
chosen
XMPP (Extensible Messaging and Presence Protocol) is an open, XML-based communication protocol primarily used for instant messaging, presence information, and real-time data exchange over the internet.
-
B.
XMPP Extension Protocols
XMPP Extension Protocols are a collection of standardized specifications (XEPs) that extend the core XMPP protocol with additional features such as messaging enhancements, presence extensions, and application-specific functionality.
-
C.
XMPP Standards Foundation
The XMPP Standards Foundation is a non-profit organization that develops and maintains open standards for the Extensible Messaging and Presence Protocol (XMPP), enabling interoperable real-time communication across the internet.
-
D.
IETF Stream
The IETF Stream is the primary publication channel through which the Internet Engineering Task Force issues its technical standards and best current practice documents as RFCs.
-
E.
STUN protocol
The STUN protocol (Session Traversal Utilities for NAT) is a network protocol that helps devices discover their public IP address and port and determine the type of NAT or firewall they are behind to enable peer-to-peer connectivity.
- 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.