Triple
T4182387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Sunda Strait |
E88222
|
entity |
| Predicate | JapaneseForcesInvolved |
P43771
|
FINISHED |
| Object | Japanese cruisers |
—
|
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 cruisers | Statement: [Battle of the Sunda Strait, JapaneseForcesInvolved, Japanese cruisers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: JapaneseForcesInvolved Context triple: [Battle of the Sunda Strait, JapaneseForcesInvolved, Japanese cruisers]
-
A.
JapaneseForceStrength
Indicates the size or magnitude of the Japanese military forces involved in a particular context or operation.
-
B.
JapaneseForceName
chosen
Indicates that an entity is known by a name used for a Japanese military or armed force.
-
C.
casualtiesJapan
Indicates that an event or action resulted in casualties (deaths and/or injuries) occurring in Japan.
-
D.
JapaneseForceComponent
Indicates that an entity functions as a component or sub-unit of a Japanese military or armed force.
-
E.
objectiveOfJapaneseForces
Indicates that a specified target, goal, or aim is the military objective pursued by Japanese forces.
- 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_69aed9477e8c81908bcb862d2db55b1d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af07078cb081909f64326b12522410 |
completed | March 9, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69af019155448190b19868583272513f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.