Triple
T920831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RSS |
E19878
|
entity |
| Predicate | hasVersion |
P455
|
FINISHED |
| Object | RSS 0.92 |
E19878
|
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: RSS 0.92 | Statement: [RSS, hasVersion, RSS 0.92]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RSS 0.92 Context triple: [RSS, hasVersion, RSS 0.92]
-
A.
RSS
chosen
RSS (Really Simple Syndication) is a web feed format that allows users and applications to automatically receive updates from websites, blogs, and other online content sources.
-
B.
RFC 9002
RFC 9002 is an IETF standard that specifies the loss detection and congestion control mechanisms for the QUIC transport protocol.
-
C.
RFC 9112
RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
-
D.
RDF
RDF (Resource Description Framework) is a standard model for data interchange on the Web that represents information as subject–predicate–object triples to enable structured, machine-readable metadata and knowledge graphs.
-
E.
RFC 9205
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
- 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3120dbc81908362158fe3ffa889 |
completed | March 1, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a826d8f9408190aa286bb809507797 |
completed | March 4, 2026, 12:34 p.m. |
Created at: March 1, 2026, 7:40 p.m.