Triple
T24491898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defence of Ceylon |
E617660
|
entity |
| Predicate | opponentOperation |
P52508
|
FINISHED |
| Object | Japanese Indian Ocean raid |
—
|
NE NERFINISHED |
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 Indian Ocean raid | Statement: [Defence of Ceylon, opponentOperation, Japanese Indian Ocean raid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentOperation Context triple: [Defence of Ceylon, opponentOperation, Japanese Indian Ocean raid]
-
A.
opposedOperation
chosen
Indicates that one operation is in conflict with, counters, or works against another operation.
-
B.
opponentStrategy
Indicates that one entity employs or represents a strategic plan specifically designed to counter or compete against another entity.
-
C.
opponentState
Indicates the condition or status that an opposing party or competitor is currently in within a given context or interaction.
-
D.
opponentInCase
Indicates that two parties are on opposing sides in the same legal case or proceeding.
-
E.
opponentObjective
Indicates that one entity is the target or goal that an opposing entity aims to counter, defeat, or prevent from succeeding.
- 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_69e2d7f4e6bc8190aec540ae3b9ed7f2 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:22 a.m.