Triple
T8486779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Date (HTTP header) |
E200849
|
entity |
| Predicate | hasAlternativeNames |
P65356
|
FINISHED |
| Object | HTTP Date header |
E200849
|
NE FINISHED |
How this triple was built (3 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: HTTP Date header | Statement: [Date (HTTP header), hasAlternativeNames, HTTP Date header]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HTTP Date header Context triple: [Date (HTTP header), hasAlternativeNames, HTTP Date header]
-
A.
RFC 3339
RFC 3339 is an Internet standard that defines a simplified, unambiguous date and time format commonly used in internet protocols and data interchange.
-
B.
Date and Time on the Internet: Timestamps
"Date and Time on the Internet: Timestamps" is an IETF standard (RFC 3339) that defines a precise, unambiguous format for representing dates and times in internet protocols, based on a profile of ISO 8601.
-
C.
Date
chosen
Date is an HTTP header field that indicates the date and time at which the message was originated, formatted according to internet date/time standards.
-
D.
ISO 8601
ISO 8601 is an international standard that defines a consistent, unambiguous format for representing dates, times, and related data in numeric form.
-
E.
RFC 7232
RFC 7232 is an HTTP/1.1 specification that defines conditional request mechanisms using validators like ETags and Last-Modified to support efficient caching and concurrency control on the web.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeNames Context triple: [Date (HTTP header), hasAlternativeNames, HTTP Date header]
-
A.
hasOfficialNameVariant
Indicates that an entity has an alternative official form or version of its name.
-
B.
hasAlternativeNameForSameCity
Indicates that one city name is an alternative or variant name referring to the same city as another name.
-
C.
hasAlternativeNameOfOrder
Indicates that one entity is an alternative or variant name used to refer to the same order as the other entity.
-
D.
hasAlternativeReferent
chosen
Indicates that an entity can also be referred to or identified by an alternative name, label, or reference.
-
E.
hasAlternativeNotation
Indicates that an entity can be represented or written in a different, equivalent form or notation.
- F. None of above.
Provenance (4 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe53c4d608190a766c0e919a4b96f |
completed | March 31, 2026, 3:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce3a45e30c8190838ac499bbc66fbd |
completed | April 2, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:13 p.m.