Triple
T12948555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Asia Squadron |
E309829
|
entity |
| Predicate | EmdenDetachedForOperations |
P107646
|
FINISHED |
| Object | Indian Ocean commerce raiding |
—
|
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: Indian Ocean commerce raiding | Statement: [East Asia Squadron, EmdenDetachedForOperations, Indian Ocean commerce raiding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EmdenDetachedForOperations Context triple: [East Asia Squadron, EmdenDetachedForOperations, Indian Ocean commerce raiding]
-
A.
aimedToBeDismantledBy
Indicates that one entity was the intended target of dismantling or disassembly by another entity.
-
B.
dismantledBy
Indicates that something has been taken apart, disassembled, or broken down by a particular agent or entity.
-
C.
dismantledIn
Indicates that an entity was taken apart, disassembled, or broken down within a specified context, such as a particular time, place, or event.
-
D.
detonatedOver
Indicates that one entity caused an explosion or detonation to occur above or over another entity or location.
-
E.
demolitionEnd
Indicates the point in time or event at which a demolition process is completed or comes to an end.
- 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97db69f548190a1a693bc0d6c191a |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97e5811f481908178fac6d2e0efcd |
completed | April 10, 2026, 10:48 p.m. |
Created at: April 9, 2026, 5:43 p.m.