Triple
T21224579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1889 |
E523056
|
entity |
| Predicate | definesConcept |
P773
|
FINISHED |
| Object | RTP mixer |
—
|
NE NERFINISHED |
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: RTP mixer | Statement: [RFC 1889, definesConcept, RTP mixer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RTP mixer Context triple: [RFC 1889, definesConcept, RTP mixer]
-
A.
RTP
RTP is the abbreviation commonly used for the Royal Thai Police, the national law enforcement agency of Thailand.
-
B.
RTP
chosen
RTP (Real-time Transport Protocol) is a network protocol designed for delivering audio and video over IP networks in real-time, commonly used in streaming, VoIP, and multimedia communication systems.
-
C.
RTP
RTP is Portugal’s main public broadcasting organization, operating national television and radio channels that play a central role in promoting and preserving Portuguese culture.
-
D.
MIXER
MIXER is an email gateway protocol that enables interoperability between X.400 and Internet mail systems, as defined in RFC 1664.
-
E.
RTMP
RTMP (Real-Time Messaging Protocol) is a streaming protocol primarily used to deliver audio, video, and data over the internet with low latency, especially in live broadcasting and interactive media applications.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734aa82c4819086cef6364619b4e9 |
completed | April 21, 2026, 8:26 a.m. |
Created at: April 16, 2026, 3:44 p.m.