Triple
T20403918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tunic of Heracles |
E500410
|
entity |
| Predicate | methodOfDelivery |
P130074
|
FINISHED |
| Object | gift |
—
|
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: gift | Statement: [tunic of Heracles, methodOfDelivery, gift]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfDelivery Context triple: [tunic of Heracles, methodOfDelivery, gift]
-
A.
deliveryType
Indicates the method or mode by which a product, service, or item is delivered or fulfilled.
-
B.
ballDeliveryMethod
Indicates the manner or technique by which a ball is delivered, passed, or thrown from one entity to another.
-
C.
deliveryModelOf
Indicates that one entity functions as the delivery model or mechanism through which another entity (such as a service, product, or program) is provided or made available.
-
D.
deliveryStyle
Indicates the manner or approach with which something (such as information, a product, or a service) is presented, communicated, or provided to its recipient.
-
E.
isDeliveredThrough
chosen
Indicates that something is transmitted, conveyed, or provided by means of a specified channel, method, or medium.
- 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_69e0b4a81bec8190b69adfdc1336a015 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6799080cc819096dc31f41d1d7b49 |
completed | April 20, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:29 a.m.