Triple
T2259202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ever Given |
E49997
|
entity |
| Predicate | deliveryDate |
P36795
|
FINISHED |
| Object | 2018-09-25 |
—
|
LITERAL 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: 2018-09-25 | Statement: [Ever Given, deliveryDate, 2018-09-25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deliveryDate Context triple: [Ever Given, deliveryDate, 2018-09-25]
-
A.
finalDeliveryDate
Indicates the date on which the last or ultimate delivery in a sequence of deliveries is scheduled or actually occurs.
-
B.
firstDeliveryDate
Indicates the date on which an item, service, or order is delivered for the first time.
-
C.
deliveredAt
Indicates the specific time or location at which something (such as a message, product, or service) is delivered.
-
D.
deliveredDuring
Indicates that one entity was delivered within the time span defined by another entity or temporal interval.
-
E.
deliveryDays
Indicates the number of days required for an item or service to be delivered from the sender to the recipient.
- F. None of above. chosen
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_69a88b01e0048190ba96431b5f990ba9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc15ad06c8190b6d0babc17015787 |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbdb34c148190b51e99f540f97204 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe86dbcc81908c72793af8fe2a4d |
completed | March 7, 2026, 5:58 a.m. |
Created at: March 4, 2026, 7:48 p.m.