Triple
T10141834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1541 |
E231599
|
entity |
| Predicate | category |
P87
|
FINISHED |
| Object | Internet Standard (historic) |
E35278
|
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: Internet Standard (historic) | Statement: [RFC 1541, category, Internet Standard (historic)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Internet Standard (historic) Context triple: [RFC 1541, category, Internet Standard (historic)]
-
A.
Internet Standards history
Internet Standards history is the chronological development and evolution of the technical specifications, protocols, and governance processes that define how the global Internet operates and interoperates.
-
B.
Internet Standard
chosen
An Internet Standard is a formal, widely implemented and stable technical specification approved by the Internet Engineering Task Force (IETF) as part of the core protocols and practices that define how the Internet operates.
-
C.
IETF Internet standards process
The IETF Internet standards process is the formal, consensus-driven procedure by which the Internet Engineering Task Force develops, reviews, and approves technical specifications to become official Internet Standards.
-
D.
Standard for the Format of ARPA Internet Text Messages
Standard for the Format of ARPA Internet Text Messages is the seminal specification that defined the syntax and structure of electronic mail messages on the early ARPANET, forming the basis for modern Internet email formats.
-
E.
RFC 1700
RFC 1700 is an Internet standards document that served as the central Assigned Numbers registry, cataloging protocol parameters such as port numbers, protocol numbers, and other key Internet identifiers.
- 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_69ca848364f881908a24366a6feec1db |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdeb2599e0819090184631e481310c |
completed | April 2, 2026, 4:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2e60e51488190a6097837eb3ce18a |
completed | April 5, 2026, 10:45 p.m. |
Created at: March 30, 2026, 9:07 p.m.