Triple
T35150518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Lamson |
E1014972
|
entity |
| Predicate | locationOfKamikazeDamage |
P75988
|
FINISHED |
| Object | off Leyte, Philippines |
—
|
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: off Leyte, Philippines | Statement: [USS Lamson, locationOfKamikazeDamage, off Leyte, Philippines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfKamikazeDamage Context triple: [USS Lamson, locationOfKamikazeDamage, off Leyte, Philippines]
-
A.
locationOfKamikazeAttack
chosen
Indicates the place where a kamikaze attack occurred or was carried out.
-
B.
kamikazeHits
Indicates that an attacking entity deliberately crashes into and strikes a target in a suicidal or self-destructive manner.
-
C.
locationOfTorpedoAttack
Indicates the place where a torpedo attack occurred or was carried out.
-
D.
wasHeavilyDamagedOn
Indicates that an entity experienced severe damage at or during a specified time or event.
-
E.
notableLocationOfDamage
Indicates the specific place where damage is prominently present or has significantly occurred.
- 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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.