Triple
T28563270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACE |
E722604
|
entity |
| Predicate | providesLeadTimeFor |
P81572
|
FINISHED |
| Object | geomagnetic storms |
—
|
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: geomagnetic storms | Statement: [ACE, providesLeadTimeFor, geomagnetic storms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesLeadTimeFor Context triple: [ACE, providesLeadTimeFor, geomagnetic storms]
-
A.
leadTimeTypical
Indicates the usual or standard amount of time that typically elapses between the initiation of a process or request and its completion or delivery.
-
B.
warningLeadTime
chosen
Indicates the amount of time in advance that a warning is issued before an event or condition occurs.
-
C.
peakDeliveryTime
Indicates the time period during which deliveries are expected to be at their highest volume or frequency.
-
D.
typicalCompletionTimeInWeeks
Indicates the usual number of weeks it takes to complete the associated task, process, or activity.
-
E.
offersDuration
Indicates that an entity provides or specifies a length of time for which something (such as a service, offer, or condition) is available or valid.
- 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 28, 2026, 4:06 a.m.