Triple
T4027625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Road |
E83628
|
entity |
| Predicate | travelTimeByCourier |
P18531
|
FINISHED |
| Object | about 7 days between Sardis and Susa |
—
|
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: about 7 days between Sardis and Susa | Statement: [Royal Road, travelTimeByCourier, about 7 days between Sardis and Susa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelTimeByCourier Context triple: [Royal Road, travelTimeByCourier, about 7 days between Sardis and Susa]
-
A.
peakDeliveryTime
Indicates the time period during which deliveries are expected to be at their highest volume or frequency.
-
B.
deliverySpeed
Indicates the rate or promptness with which an item, service, or information is delivered from a source to a recipient.
-
C.
deliveryStandard
Indicates the agreed level, method, or timeframe by which a delivery is to be carried out between parties.
-
D.
deliveryDays
chosen
Indicates the number of days required for an item or service to be delivered from the sender to the recipient.
-
E.
deliveredBy
Indicates that something (such as a product, message, or service) is brought, transported, or provided to its destination by a specified agent or carrier.
- 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_69aed92e29ac819080f7a98b594fec05 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaeec44881909a6c008eeae204df |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fc78ec819092d4dab88d85a141 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:36 p.m.