Triple
T4617203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3339 |
E100895
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 2445 (with respect to timestamp format alignment aspects) |
E100895
|
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 2445 (with respect to timestamp format alignment aspects) | Statement: [RFC 3339, obsoletes, RFC 2445 (with respect to timestamp format alignment aspects)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2445 (with respect to timestamp format alignment aspects) Context triple: [RFC 3339, obsoletes, RFC 2445 (with respect to timestamp format alignment aspects)]
-
A.
RFC 3339
chosen
RFC 3339 is an Internet standard that defines a simplified, unambiguous date and time format commonly used in internet protocols and data interchange.
-
B.
RFC 6557 (tz database procedures)
RFC 6557 (tz database procedures) is an IETF document that defines the policies and processes for maintaining and updating the IANA time zone (tz) database.
-
C.
ISO 8601
ISO 8601 is an international standard that defines a consistent, unambiguous format for representing dates, times, and related data in numeric form.
-
D.
RFC 1441
RFC 1441 is an early standards-track document in the Simple Network Management Protocol (SNMP) framework that was later superseded by RFC 1901 as the protocol evolved.
-
E.
RFC 1447
RFC 1447 is an early Internet standards document that specified mechanisms for managing SNMPv2 network management protocols before being superseded by later revisions.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e098c08190b769e76937dff700 |
completed | March 20, 2026, 2:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bdfa916f4c8190a53bb37ff46ed0b5 |
completed | March 21, 2026, 1:55 a.m. |
Created at: March 20, 2026, 1:12 p.m.