Triple
T920832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RSS |
E19878
|
entity |
| Predicate | hasVersion |
P455
|
FINISHED |
| Object | RSS 1.0 |
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 1.0 | Statement: [RSS, hasVersion, RSS 1.0]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RSS 1.0 Context triple: [RSS, hasVersion, RSS 1.0]
-
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.
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.
-
C.
RDFS
RDFS (RDF Schema) is a semantic web vocabulary language used to define the structure, classes, and properties of RDF data.
-
D.
RFC 9001
RFC 9001 is an IETF standard that specifies how the TLS 1.3 protocol is used to secure QUIC connections, defining the cryptographic handshake and key management for QUIC.
-
E.
RFC 2068
RFC 2068 is an early Internet standards document that specifies the HTTP/1.1 protocol, detailing its methods, headers, and overall message structure for web communication.
- 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_69a7cf6486d88190b53cd743b08eef33 |
completed | March 4, 2026, 6:21 a.m. |
Created at: March 1, 2026, 7:40 p.m.