Triple
T21264784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5991 |
E524097
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 4380 |
—
|
NE NERFINISHED |
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 4380 | Statement: [RFC 5991, obsoletes, RFC 4380]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 4380 Context triple: [RFC 5991, obsoletes, RFC 4380]
-
A.
RFC 4380
chosen
RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
-
B.
RFC 3980
RFC 3980 is an Internet Engineering Task Force (IETF) document that previously specified aspects of the iSCSI (Internet Small Computer Systems Interface) protocol before being superseded by RFC 7143.
-
C.
RFC 3380
RFC 3380 is an Internet Engineering Task Force (IETF) document that defines additional features and extensions for the Internet Printing Protocol (IPP).
-
D.
RFC 4038
RFC 4038 is an IETF document that provides guidance and considerations for the transition from IPv4 to IPv6 in existing network environments.
-
E.
RFC 4330
RFC 4330 is an Internet Engineering Task Force (IETF) specification that defines a simple network time protocol (SNTP) for synchronizing computer clocks over IP networks.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735ea74e0819099d724de95996c90 |
completed | April 21, 2026, 8:31 a.m. |
Created at: April 16, 2026, 4 p.m.