Triple
T12069779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .us |
E287391
|
entity |
| Predicate | relatedStandard |
P37
|
FINISHED |
| Object | RFC 920 |
E819964
|
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 920 | Statement: [.us, relatedStandard, RFC 920]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 920 Context triple: [.us, relatedStandard, RFC 920]
-
A.
RFC 920
chosen
RFC 920 is an early Internet standards document that defines the procedures and requirements for registering and managing top-level domains in the Domain Name System (DNS).
-
B.
RFC 990
RFC 990 is an Internet standards document that updated and replaced RFC 870, refining technical specifications within the early TCP/IP protocol suite.
-
C.
RFC 950
RFC 950 is an Internet standard that defines the procedures and format for subnetting IP networks, extending the original IPv4 addressing scheme.
-
D.
RFC 974
RFC 974 is an early Internet standard that defined the original mechanisms for mail routing and the use of MX records in the Domain Name System (DNS).
-
E.
RFC 0960
RFC 0960 is an early Internet standards document that specified aspects of TCP/IP networking behavior later superseded by RFC 1122.
- 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90457fd488190b311ed69d2aebdf9 |
completed | April 10, 2026, 2:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f65ccc788190942e16c56f2a495f |
completed | May 2, 2026, 1:04 p.m. |
Created at: April 8, 2026, 9:48 p.m.