Triple
T25842331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Attack-class submarine |
E650968
|
entity |
| Predicate | intendedOperationalTheatre |
P710
|
FINISHED |
| Object | Indo-Pacific region |
—
|
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: Indo-Pacific region | Statement: [Attack-class submarine, intendedOperationalTheatre, Indo-Pacific region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedOperationalTheatre Context triple: [Attack-class submarine, intendedOperationalTheatre, Indo-Pacific region]
-
A.
fieldOfOperation
Indicates the domain, area, or scope within which an entity operates or carries out its primary activities.
-
B.
countryOfDeployment
Indicates the country where an entity (such as a person, unit, or asset) is currently or was assigned, stationed, or operating.
-
C.
hasPrimaryTheatreOfWar
Indicates that an armed conflict or military operation is chiefly conducted within a particular geographic theatre or region of war.
-
D.
militaryTheater
chosen
Indicates that an entity is a geographic or operational area where military operations or campaigns are conducted.
-
E.
primaryIslandOfOperation
Indicates that an entity mainly conducts its activities or operations on a specified island.
- 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_69e7ab38086081908f3a8e7e0c6efd83 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 22, 2026, 7:50 a.m.