Triple
T8611377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet Printing Protocol |
E203920
|
entity |
| Predicate | definedInRFC |
P5655
|
FINISHED |
| Object | RFC 2911 |
E745322
|
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 2911 | Statement: [Internet Printing Protocol, definedInRFC, RFC 2911]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2911 Context triple: [Internet Printing Protocol, definedInRFC, RFC 2911]
-
A.
RFC 2911
chosen
RFC 2911 is the core specification that defines the Internet Printing Protocol (IPP) model, operations, and attributes used for network printing.
-
B.
RFC 2910
RFC 2910 is an IETF specification that defines the Internet Printing Protocol/1.1 model and encoding for network printing.
-
C.
RFC 2811
RFC 2811 is an Internet standards document that specifies the architecture and operation of Internet Relay Chat (IRC) channel management.
-
D.
RFC 2481
RFC 2481 is an early experimental specification that introduced Explicit Congestion Notification (ECN) for IP and TCP to signal network congestion without packet loss.
-
E.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46fc31e08190aab5ab8f92f3315c |
completed | March 31, 2026, 10:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cecc8b99cc8190b319a435f456ec05 |
completed | April 2, 2026, 8:07 p.m. |
Created at: March 30, 2026, 6:25 p.m.