Triple
T35517266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Action of 15 May 1917 |
E1026451
|
entity |
| Predicate | AlliedShipTypeTargeted |
P56001
|
FINISHED |
| Object | armed drifter |
—
|
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: armed drifter | Statement: [Action of 15 May 1917, AlliedShipTypeTargeted, armed drifter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AlliedShipTypeTargeted Context triple: [Action of 15 May 1917, AlliedShipTypeTargeted, armed drifter]
-
A.
targetedShip
chosen
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.
primaryAlliedCruiser
Indicates that one entity serves as the main or principal allied cruiser associated with another entity.
-
C.
AlliedShipsInvolved
Indicates that allied ships participated in or were involved in the specified event or operation.
-
D.
navalForceTargeted
Indicates that a naval force is selected or designated as the target of an action or operation.
-
E.
navalVesselsAlliedApprox
Indicates that two or more naval vessels are approximately allied, suggesting a cooperative or friendly relationship without specifying a precise or formal alliance.
- 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:04 p.m.