Triple
T18770438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Date and Time on the Internet: Timestamps |
E459004
|
entity |
| Predicate | RFCNumber |
P3247
|
FINISHED |
| Object | RFC 3339 |
—
|
NE NERFINISHED |
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 3339 | Statement: [Date and Time on the Internet: Timestamps, RFCNumber, RFC 3339]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 3339 Context triple: [Date and Time on the Internet: Timestamps, RFCNumber, RFC 3339]
-
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.
ISO 8601
ISO 8601 is an international standard that defines a consistent, unambiguous format for representing dates, times, and related data in numeric form.
-
C.
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.
-
D.
RFC 2822
RFC 2822 is an Internet standard that defines the format for text-based email messages, updating and replacing the earlier RFC 822 specification.
-
E.
RFC 8259
RFC 8259 is the IETF specification that formally defines the JSON (JavaScript Object Notation) data interchange format, including its syntax and semantics.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e58d8782b4819080513fb46798c4db |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 10, 2026, 11:52 a.m.