Triple
T10601759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1908 |
E275764
|
entity |
| Predicate | updates |
P4061
|
FINISHED |
| Object | RFC 1157 |
E35269
|
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 1157 | Statement: [RFC 1908, updates, RFC 1157]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1157 Context triple: [RFC 1908, updates, RFC 1157]
-
A.
RFC 1157
chosen
RFC 1157 is the Internet standard document that specifies the Simple Network Management Protocol (SNMP) used for managing devices on IP networks.
-
B.
RFC 1457
RFC 1457 is an early Internet standards document that specified guidelines and mechanisms related to network management within the SNMP framework before being superseded by later updates.
-
C.
RFC 1327
RFC 1327 is an Internet standards document that specifies mechanisms for interworking between X.400 electronic mail and Internet (RFC 822/SMTP) email systems.
-
D.
RFC 1072
RFC 1072 is an early TCP/IP standards document that introduced experimental TCP extensions for high-performance and long-delay networks.
-
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 (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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6ded61d5c8190b13890c964b59949 |
completed | April 8, 2026, 11:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d95ea8f1688190aa36e29b52667d26 |
completed | April 10, 2026, 8:33 p.m. |
Created at: April 8, 2026, 7:31 p.m.