Triple
T25293223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyushu Campaign |
E634144
|
entity |
| Predicate | hasPrimaryAdversaryDomain |
P68850
|
FINISHED |
| Object | Satsuma Domain |
—
|
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: Satsuma Domain | Statement: [Kyushu Campaign, hasPrimaryAdversaryDomain, Satsuma Domain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryAdversaryDomain Context triple: [Kyushu Campaign, hasPrimaryAdversaryDomain, Satsuma Domain]
-
A.
hasMainAdversary
chosen
Indicates that an entity’s primary or most significant opponent, rival, or enemy is another specified entity.
-
B.
hasOpposingAgent
Indicates that an entity is opposed or counteracted by another agent in a given context or interaction.
-
C.
primaryAdversaryContext
Indicates the main opposing force or conflict-driving element that defines the central adversarial situation within a given context.
-
D.
hasPrimaryTactic
Indicates that an entity is associated with its main or most commonly used tactic or method of operation.
-
E.
primaryAdversaryImplied
Indicates that an entity is understood or suggested, rather than explicitly stated, to be the main opponent or chief adversary of another entity.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 21, 2026, 1:22 p.m.