Triple
T12269002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 9293 |
E292423
|
entity |
| Predicate | series |
P1761
|
FINISHED |
| Object | STD 7 |
E207718
|
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: STD 7 | Statement: [RFC 9293, series, STD 7]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: STD 7 Context triple: [RFC 9293, series, STD 7]
-
A.
STD 7
chosen
STD 7 is an Internet Standards Track specification in the IETF standards series, corresponding to RFC 2131, which defines the Dynamic Host Configuration Protocol (DHCP) for automated IP address assignment and configuration.
-
B.
STD 5
STD 5 is the Internet Standard that defines the core Internet Protocol (IP), as specified primarily in RFC 791.
-
C.
STD 3
STD 3 is an Internet Standard that specifies the core Internet Protocol (IP) used for addressing and routing packets across interconnected networks.
-
D.
STD 1
STD 1 is an early Internet Standard that specifies the foundational Internet Protocol (IP), defining how data packets are addressed and routed across interconnected networks.
-
E.
STD 16
STD 16 is an Internet Standards Track document that specifies a core protocol or set of protocols within the official Internet Standards (STD) series maintained by the IETF.
- 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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91cdea6e881908e13f8259bad6ddc |
completed | April 10, 2026, 3:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e6799088190a5644267733ca2e5 |
completed | May 2, 2026, 3:55 p.m. |
Created at: April 8, 2026, 9:52 p.m.