Triple
T12513839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baseball5 |
E299146
|
entity |
| Predicate | ballDeliveryMethod |
P105354
|
FINISHED |
| Object | hit by hand |
—
|
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: hit by hand | Statement: [Baseball5, ballDeliveryMethod, hit by hand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballDeliveryMethod Context triple: [Baseball5, ballDeliveryMethod, hit by hand]
-
A.
deliveryType
Indicates the method or mode by which a product, service, or item is delivered or fulfilled.
-
B.
deliverySystem
Indicates a system, method, or mechanism by which something (such as a product, service, or substance) is transported, distributed, or conveyed from a source to a recipient.
-
C.
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.
-
D.
deliveryStandard
Indicates the agreed level, method, or timeframe by which a delivery is to be carried out between parties.
-
E.
deliveryMode
Indicates the method or channel through which something (such as a product, service, or information) is delivered or provided.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d954b715fc819091fa84430be46273 |
completed | April 10, 2026, 7:51 p.m. |
Created at: April 8, 2026, 9:57 p.m.