Triple
T35965779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Chester (CA-27) |
E1040137
|
entity |
| Predicate | locationDamaged |
P87330
|
FINISHED |
| Object | near the Solomon Islands |
—
|
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: near the Solomon Islands | Statement: [USS Chester (CA-27), locationDamaged, near the Solomon Islands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationDamaged Context triple: [USS Chester (CA-27), locationDamaged, near the Solomon Islands]
-
A.
notableLocationOfDamage
chosen
Indicates the specific place where damage is prominently present or has significantly occurred.
-
B.
damagedIn
Indicates that an entity has suffered harm, impairment, or destruction as a result of a specified event, process, or condition.
-
C.
damLocation
Indicates the geographic place where a dam is situated or constructed.
-
D.
damagedBy
Indicates that one entity has caused harm, impairment, or deterioration to another entity.
-
E.
lossLocation
Indicates the place or setting where a loss event occurs or is recorded.
- 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.