Triple
T11422079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1670 |
E270646
|
entity |
| Predicate | hasIdentifier |
P1285
|
FINISHED |
| Object | RFC1670 |
E270646
|
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: RFC1670 | Statement: [RFC 1670, hasIdentifier, RFC1670]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC1670 Context triple: [RFC 1670, hasIdentifier, RFC1670]
-
A.
RFC 1670
chosen
RFC 1670 is an early Internet standards document related to network protocols that was later superseded by RFC 1901.
-
B.
RFC 1870
RFC 1870 is an earlier Internet standards document that defined support for extended SMTP message sizes before being superseded by RFC 2821.
-
C.
RFC 1667
RFC 1667 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
D.
RFC 1657
RFC 1657 is an early Internet standards document that defined SNMPv2 Management Information Base (MIB) extensions for managing BGP-4 routing protocol implementations.
-
E.
RFC 1660
RFC 1660 is an early Internet standards document that specified an initial version of the Simple Network Management Protocol (SNMP) over OSI transport services before being superseded by later RFCs.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d801b357e88190ace56d36a945688f |
completed | April 9, 2026, 7:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5b8a1e88c8190994bea88a0490e60 |
completed | April 20, 2026, 5:24 a.m. |
Created at: April 8, 2026, 9:34 p.m.