Triple
T8853589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YANG |
E210696
|
entity |
| Predicate | definedInStandard |
P1371
|
FINISHED |
| Object | RFC 6020 |
E38999
|
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 6020 | Statement: [YANG, definedInStandard, RFC 6020]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 6020 Context triple: [YANG, definedInStandard, RFC 6020]
-
A.
RFC 6020
chosen
RFC 6020 is the IETF specification that defines the YANG data modeling language used for network configuration and management protocols such as NETCONF.
-
B.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
-
C.
RFC 5620
RFC 5620 is an IETF standards document that defines a framework for managing and monitoring MPLS-based transport networks.
-
D.
RFC 6410
RFC 6410 is an Internet Engineering Task Force (IETF) document that streamlines and updates the process for advancing technical specifications to Internet Standard status within the Internet Standards Process.
-
E.
RFC 6062
RFC 6062 is an IETF specification that extends the TURN protocol to support TCP relaying for applications operating across NATs and firewalls.
- 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_69ca838a424c8190b1ecac115c2927e7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60c55e348190957b3bbb7397e380 |
completed | April 1, 2026, 12:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfa09557dc81908b5690bf5c392528 |
completed | April 3, 2026, 11:12 a.m. |
Created at: March 30, 2026, 6:49 p.m.