Triple
T9312873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7720 |
E224045
|
entity |
| Predicate | identifier |
P3732
|
FINISHED |
| Object | RFC 7720 |
E224045
|
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 7720 | Statement: [RFC 7720, identifier, RFC 7720]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 7720 Context triple: [RFC 7720, identifier, RFC 7720]
-
A.
RFC 7720
chosen
RFC 7720 is an IETF standards document that specifies the technical and operational requirements for the DNS Root Server System.
-
B.
RFC 7320
RFC 7320 is an Internet Engineering Task Force (IETF) document that provided guidelines and best practices for the use and management of URI registries in Internet protocols.
-
C.
RFC 7472
RFC 7472 is an Internet Engineering Task Force (IETF) specification that defines extensions and mechanisms for the Internet Printing Protocol (IPP), enhancing network printing capabilities and interoperability.
-
D.
RFC 5620
RFC 5620 is an IETF standards document that defines a framework for managing and monitoring MPLS-based transport networks.
-
E.
RFC 7950
RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20ae96e481909a1af9ea1c91f2b2 |
completed | April 1, 2026, 1:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0c7a0adc4819097ac906f03f0188e |
completed | April 4, 2026, 8:11 a.m. |
Created at: March 30, 2026, 7:37 p.m.