Triple
T8421852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1519 |
E198873
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RFC 4633 |
E733096
|
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 4633 | Statement: [RFC 1519, relatedTo, RFC 4633]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 4633 Context triple: [RFC 1519, relatedTo, RFC 4633]
-
A.
RFC 4633
chosen
RFC 4633 is an Internet Engineering Task Force (IETF) standard that updates and refines the Classless Inter-Domain Routing (CIDR) architecture for IP addressing and routing.
-
B.
RFC 4833
RFC 4833 is an Internet Engineering Task Force (IETF) document that specifies extensions to the Network Time Protocol (NTP) to support leap seconds and related timekeeping issues.
-
C.
RFC 4033
RFC 4033 is an Internet standard that specifies the security extensions for the Domain Name System (DNSSEC), defining mechanisms for authenticating DNS data.
-
D.
RFC 3445
RFC 3445 is an earlier Internet Engineering Task Force (IETF) specification related to DNS security that was later superseded by RFC 4033.
-
E.
RFC 2433
RFC 2433 is an older Internet Engineering Task Force (IETF) specification that was later superseded by RFC 4250 as part of updates to SSH-related protocol definitions.
- 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_69ca8312d63c8190bf133b676b44a385 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb859e22f88190a61e7dd6537644b0 |
completed | March 31, 2026, 8:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce1d469a148190a6f018f758cba5eb |
completed | April 2, 2026, 7:39 a.m. |
Created at: March 30, 2026, 6:06 p.m.