Triple
T9244394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1452 |
E222149
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | STD 16 |
E786906
|
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 16 | Statement: [RFC 1452, obsoletedBy, STD 16]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: STD 16 Context triple: [RFC 1452, obsoletedBy, STD 16]
-
A.
STD 16
chosen
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.
-
B.
STD 17
STD 17 is an Internet Standards Track specification series that defines the core structure and management information base (MIB) for the Simple Network Management Protocol (SNMP).
-
C.
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.
-
D.
STD 5
STD 5 is the Internet Standard that defines the core Internet Protocol (IP), as specified primarily in RFC 791.
-
E.
STD 37
STD 37 is an Internet Standard that defines a core protocol or specification within the official Internet standards 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_69ca83ee26cc81909ac624e190597d6d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cd03edd37481908ea2f6dac354f04f |
completed | April 1, 2026, 11:39 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d09bca80a481908038fee287989a54 |
completed | April 4, 2026, 5:04 a.m. |
Created at: March 30, 2026, 7:30 p.m.