Triple
T5035812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Slam bomb |
E113416
|
entity |
| Predicate | coolingTimeForFilling |
P17474
|
FINISHED |
| Object | several weeks |
—
|
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: several weeks | Statement: [Grand Slam bomb, coolingTimeForFilling, several weeks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coolingTimeForFilling Context triple: [Grand Slam bomb, coolingTimeForFilling, several weeks]
-
A.
coolingRequirement
Indicates that an entity requires or is subject to a specific amount or type of cooling to operate within acceptable conditions.
-
B.
brewingTime
Indicates the duration required to brew or prepare a beverage or similar concoction.
-
C.
coolingStrategy
Indicates the method or approach used to reduce or control temperature in a system or environment.
-
D.
timeToComplete
chosen
Indicates the duration required for an entity or process to be fully completed.
-
E.
typicalCookingTime
Indicates the usual duration required to cook something under standard or commonly accepted conditions.
- 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_69bd44384298819089c49e7c330ec7b8 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73b9ad488190a2a8c4da8858eb91 |
completed | March 20, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69bd71509e9c8190a60c1d8d04936a12 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.