Triple
T21344342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Campbeltown |
E526288
|
entity |
| Predicate | explosionTimeDelay |
P100276
|
FINISHED |
| Object | several hours after impact |
—
|
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 hours after impact | Statement: [HMS Campbeltown, explosionTimeDelay, several hours after impact]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explosionTimeDelay Context triple: [HMS Campbeltown, explosionTimeDelay, several hours after impact]
-
A.
explosionDelay
chosen
Indicates a temporal offset between the triggering of an explosion event and the moment the explosion actually occurs.
-
B.
timeOfDetonation
Indicates the specific point in time at which a detonation event occurs.
-
C.
explosionType
Indicates the specific kind or category of explosion associated with an event or entity.
-
D.
explosionOccurred
Indicates that an explosion event has taken place at a specific time and/or location.
-
E.
explosionMechanism
Indicates the specific process or mechanism by which an explosion is initiated or occurs.
- 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_69e0b51c33048190ab27cede74ef798c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8a85274f481909e699b390bed9350 |
completed | April 22, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:44 p.m.