Triple
T37250636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese light cruiser Tama |
E923976
|
entity |
| Predicate | battleDamagedAt |
P16536
|
FINISHED |
| Object | Battle of Cape Engaño |
—
|
NE NERFINISHED |
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: Battle of Cape Engaño | Statement: [Japanese light cruiser Tama, battleDamagedAt, Battle of Cape Engaño]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleDamagedAt Context triple: [Japanese light cruiser Tama, battleDamagedAt, Battle of Cape Engaño]
-
A.
battleOccurredOn
Indicates that a specific battle took place at or on a particular location or date.
-
B.
damagedBy
Indicates that one entity has caused harm, impairment, or deterioration to another entity.
-
C.
woundedAt
Indicates that an entity was injured or harmed at a specific place or during a particular event.
-
D.
warDamage
chosen
Indicates damage that was caused as a direct consequence of war or armed conflict.
-
E.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/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_69f76eaabb4c819093b751b139dad551 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:15 p.m.