Triple
T6409009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Real-time Transport Control Protocol |
E127658
|
entity |
| Predicate | predecessorRFC |
P70468
|
FINISHED |
| Object | RFC 1889 |
E523056
|
NE FINISHED |
How this triple was built (3 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 1889 | Statement: [Real-time Transport Control Protocol, predecessorRFC, RFC 1889]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1889 Context triple: [Real-time Transport Control Protocol, predecessorRFC, RFC 1889]
-
A.
RFC 1889
chosen
RFC 1889 was the original specification of the Real-time Transport Protocol (RTP) for delivering audio and video over IP networks, later obsoleted by updated standards.
-
B.
RFC 1869
RFC 1869 is an early Internet standard that introduced the Extended Simple Mail Transfer Protocol (ESMTP) framework for adding optional extensions to SMTP.
-
C.
RFC 1908
RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
-
D.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
E.
RFC 1668
RFC 1668 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specifications evolved.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorRFC Context triple: [Real-time Transport Control Protocol, predecessorRFC, RFC 1889]
-
A.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
B.
predecessorName
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
-
C.
predecessorStatus
Indicates that one entity’s status is determined by, or directly follows from, the status of a preceding entity in a sequence or process.
-
D.
predecessorFamily
Indicates that one family is the earlier or ancestral family from which another family descends or follows.
-
E.
predecessorVersion
Indicates that one entity is an earlier or prior version in a version sequence relative to another entity.
- F. None of above. chosen
Provenance (5 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_69c0083723d88190b1e37b19df162c08 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068cdf25881908d42a5d979637ad6 |
completed | March 22, 2026, 10:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c638b38c888190aa2433173db64c90 |
completed | March 27, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69c060f40ecc8190b1df17b96767675c |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623d23448190a75cf5d802fc0a02 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:41 p.m.