Triple
T10416826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1659 |
E245538
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 1284 |
E200280
|
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 1284 | Statement: [RFC 1659, obsoletes, RFC 1284]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1284 Context triple: [RFC 1659, obsoletes, RFC 1284]
-
A.
Printer Access Protocol
chosen
Printer Access Protocol is a network printing protocol used in AppleTalk environments to manage communication between computers and printers.
-
B.
ANSI X3.226-1994
ANSI X3.226-1994 is the American National Standards Institute specification that formally defines the Common Lisp programming language.
-
C.
EIA-449
EIA-449 is a telecommunications standard that defines electrical and mechanical interface characteristics for high-speed serial data communication between data terminal equipment and data circuit-terminating equipment.
-
D.
RFC 1451
RFC 1451 is an early Internet standards document related to network management that was later superseded by RFC 1901.
-
E.
Line Printer Daemon protocol
The Line Printer Daemon protocol is an older network printing protocol, originally from BSD Unix, used to submit and manage print jobs over TCP/IP.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea1194e08190a18c3b3002147493 |
completed | April 7, 2026, 11:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d7fc0dd480819082edcc49a245ad4f |
completed | April 9, 2026, 7:20 p.m. |
Created at: April 6, 2026, 12:10 p.m.