Triple
T11801147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1869 |
E280627
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RFC 1870 |
E772836
|
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: RFC 1870 | Statement: [RFC 1869, relatedTo, RFC 1870]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1870 Context triple: [RFC 1869, relatedTo, RFC 1870]
-
A.
RFC 1870
chosen
RFC 1870 is an earlier Internet standards document that defined support for extended SMTP message sizes before being superseded by RFC 2821.
-
B.
RFC 1670
RFC 1670 is an early Internet standards document related to network protocols that was later superseded by RFC 1901.
-
C.
RFC 1847
RFC 1847 is an early Internet standards document that defined a general framework for security multiparts in MIME email, laying groundwork for later secure messaging specifications.
-
D.
RFC 1889
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.
-
E.
RFC 1730
RFC 1730 is an early specification of the Internet Message Access Protocol (IMAP) that was later superseded by RFC 3501.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5a4512c8190b7782e1dee053000 |
completed | April 10, 2026, 7:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f166dbcb848190a5942ec00a2ca2f9 |
completed | April 29, 2026, 2:03 a.m. |
Created at: April 8, 2026, 9:42 p.m.