Triple
T6966685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "Dy-no-mite!" |
E161506
|
entity |
| Predicate | deliveryStyle |
P73829
|
FINISHED |
| Object | elongated pronunciation of "dynamite" |
—
|
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: elongated pronunciation of "dynamite" | Statement: ["Dy-no-mite!", deliveryStyle, elongated pronunciation of "dynamite"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deliveryStyle Context triple: ["Dy-no-mite!", deliveryStyle, elongated pronunciation of "dynamite"]
-
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.
deliveryStandard
Indicates the agreed level, method, or timeframe by which a delivery is to be carried out between parties.
-
D.
deliveryMode
Indicates the method or channel through which something (such as a product, service, or information) is delivered or provided.
-
E.
servingStyle
Indicates how something (typically food or drink) is presented or offered for consumption or use.
- 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_69c68853cff881908439d488924a8283 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db121174819098e73e45f6c9cc91 |
completed | March 27, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c0b0a08190b262dfc94992994d |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d9bb57e88190a3a7cec34e3b617f |
completed | March 27, 2026, 7:25 p.m. |
Created at: March 27, 2026, 2:30 p.m.