Triple
T13203365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RMS Olympic |
E314295
|
entity |
| Predicate | orderDate |
P6878
|
FINISHED |
| Object | 1907-09-17 |
—
|
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: 1907-09-17 | Statement: [RMS Olympic, orderDate, 1907-09-17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderDate Context triple: [RMS Olympic, orderDate, 1907-09-17]
-
A.
deliveryDate
Indicates the specific date on which a product, service, or item is scheduled or expected to be delivered.
-
B.
dateOf
chosen
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
C.
dateReceived
Indicates the point in time when something (such as a message, item, or document) was received by a recipient.
-
D.
openedForDeliveriesDate
Indicates the date on which something (such as a location or service) became available to accept deliveries.
-
E.
firstDeliveryDate
Indicates the date on which an item, service, or order is delivered for the first time.
- F. None of above.
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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc6bc108190b5a6a265bf6e9fd4 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:17 p.m.