Triple
T27017544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Liscome Bay |
E680574
|
entity |
| Predicate | explosionLocation |
P18705
|
FINISHED |
| Object | after bomb stowage |
—
|
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: after bomb stowage | Statement: [USS Liscome Bay, explosionLocation, after bomb stowage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explosionLocation Context triple: [USS Liscome Bay, explosionLocation, after bomb stowage]
-
A.
detonationPosition
Indicates the specific location or coordinates at which a detonation occurs or is intended to occur.
-
B.
explosionOccurred
Indicates that an explosion event has taken place at a specific time and/or location.
-
C.
bombingLocation
chosen
Indicates the place where a bombing event occurs or is carried out.
-
D.
explosionAltitude
Indicates the height above a reference surface at which an explosion occurs or is triggered.
-
E.
detonatedOver
Indicates that one entity caused an explosion or detonation to occur above or over another entity or location.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 7:07 a.m.