Triple
T25580401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunder |
E641224
|
entity |
| Predicate | canHaveDurationUpTo |
P24237
|
FINISHED |
| Object | several minutes (for rolling thunder) |
—
|
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 minutes (for rolling thunder) | Statement: [Thunder, canHaveDurationUpTo, several minutes (for rolling thunder)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canHaveDurationUpTo Context triple: [Thunder, canHaveDurationUpTo, several minutes (for rolling thunder)]
-
A.
hasDurationType
Indicates that something is associated with a specific kind or category of duration (e.g., temporary, permanent, short-term, long-term).
-
B.
possibleDuration
chosen
Indicates the range or specific length of time that an action, event, or state can last or is allowed to last.
-
C.
hasDurationCharacteristic
Indicates that something possesses a specific temporal property, such as length, span, or persistence over time.
-
D.
hasApproximateDuration
Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
-
E.
hasOfficialDuration
Indicates the formally defined length of time associated with an event, process, or entity.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f934be208190aed5a7f6a44b6b83 |
completed | May 2, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69f4684442248190afe7677e56363e7f |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 4:11 p.m.