Triple
T4812588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinking of HMS Repulse |
E107105
|
entity |
| Predicate | shipTypeTargeted |
P8971
|
FINISHED |
| Object | battlecruiser |
—
|
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: battlecruiser | Statement: [Sinking of HMS Repulse, shipTypeTargeted, battlecruiser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipTypeTargeted Context triple: [Sinking of HMS Repulse, shipTypeTargeted, battlecruiser]
-
A.
targetedShip
Indicates that one entity has selected or designated a particular ship as the focus of its attention or action, such as for attack, tracking, or interaction.
-
B.
shipTypeInvolved
chosen
Indicates that a particular type or class of ship is involved or participates in a specified event, situation, or relationship.
-
C.
targetedAircraft
Indicates that one entity has selected or designated an aircraft as the object of an attack, tracking, or other directed action.
-
D.
shipUsed
Indicates that a particular ship was employed or utilized in carrying out an event, activity, or operation.
-
E.
shipClass
Indicates the classification or type category to which a particular ship belongs.
- 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_69bd43f779448190b92885cb70abb6c2 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1dfa3481909d240d50ed0ee38c |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:23 p.m.