Triple
T37119369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS John C. Butler |
E919204
|
entity |
| Predicate | outgunnedBy |
P187168
|
FINISHED |
| Object | Japanese battleships at Battle off Samar |
—
|
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: Japanese battleships at Battle off Samar | Statement: [USS John C. Butler, outgunnedBy, Japanese battleships at Battle off Samar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outgunnedBy Context triple: [USS John C. Butler, outgunnedBy, Japanese battleships at Battle off Samar]
-
A.
sometimesOutmatchedBy
Indicates that one entity is occasionally surpassed or defeated by another in ability, performance, or competition.
-
B.
armedAgainst
Indicates that one entity is equipped with weapons or defensive capabilities specifically in preparation for potential conflict with another entity.
-
C.
armed
Indicates that an entity is equipped with or carrying a weapon or weapons.
-
D.
weaponUsedAgainst
Indicates that a particular weapon or instrument is employed in an act of aggression, attack, or harm directed toward a specific target or entity.
-
E.
armedBy
Indicates that one entity is supplied with weapons, equipment, or armaments by another entity.
- F. None of above. chosen
Provenance (4 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_69f76e9c57148190ba789dd059645bb9 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb344ba5408190a6fe8face293d88b |
completed | May 6, 2026, 12:30 p.m. |
Created at: May 3, 2026, 4:15 p.m.