Triple
T21091523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 761 |
E519648
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RFC 791 |
—
|
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: RFC 791 | Statement: [RFC 761, relatedTo, RFC 791]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 791 Context triple: [RFC 761, relatedTo, RFC 791]
-
A.
RFC 791
chosen
RFC 791 is the foundational Internet standard that specifies the design, structure, and operation of the Internet Protocol version 4 (IPv4).
-
B.
RFC 792
RFC 792 is the Internet standard document that specifies the Internet Control Message Protocol (ICMP), which is used for network diagnostics and error reporting in IP networks.
-
C.
RFC 793
RFC 793 is the foundational Internet standard that defines the Transmission Control Protocol (TCP), specifying how reliable, ordered, and error-checked data transmission works between hosts on an IP network.
-
D.
RFC 879
RFC 879 is an early Internet standard document that specifies details of the Transmission Control Protocol (TCP), contributing to the foundational design of reliable transport on the Internet.
-
E.
RFC 1119
RFC 1119 is an early specification in the Network Time Protocol (NTP) series that was later superseded by RFC 1305.
- 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7094f6ebc8190a90b014755a9d4a6 |
completed | April 21, 2026, 5:21 a.m. |
Created at: April 16, 2026, 2:51 p.m.