Triple
T31224796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cold War-era Royal Navy |
E796108
|
entity |
| Predicate | primaryAdversaryNavy |
P53687
|
FINISHED |
| Object | Soviet Navy |
E42093
|
NE 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: Soviet Navy | Statement: [Cold War-era Royal Navy, primaryAdversaryNavy, Soviet Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAdversaryNavy Context triple: [Cold War-era Royal Navy, primaryAdversaryNavy, Soviet Navy]
-
A.
primaryAntagonistShip
Indicates that one ship serves as the main opposing or enemy vessel in relation to another entity or context.
-
B.
opponentFleet
chosen
Indicates that one fleet is in an adversarial or opposing relationship to another fleet.
-
C.
primaryEnemyForces
Indicates that the related entities constitute the main opposing or hostile forces in a conflict or competitive situation.
-
D.
navalOpposition
Indicates a relationship where one party actively resists, confronts, or acts against another using naval or maritime military forces.
-
E.
navalForceTargeted
Indicates that a naval force is selected or designated as the target of an action or operation.
- F. None of above.
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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a295932676c81909e15816aa9db36ff |
completed | June 10, 2026, 12:31 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:10 p.m.