Triple
T34849577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strengthening British naval power in the Mediterranean |
E1004561
|
entity |
| Predicate | hasKeyOpponent |
P13136
|
FINISHED |
| Object | Kingdom of Spain |
—
|
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: Kingdom of Spain | Statement: [Strengthening British naval power in the Mediterranean, hasKeyOpponent, Kingdom of Spain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyOpponent Context triple: [Strengthening British naval power in the Mediterranean, hasKeyOpponent, Kingdom of Spain]
-
A.
keyOpponents
chosen
Indicates that the subject has primary or most significant opponents identified by the object.
-
B.
hasKeyBattle
Indicates that an entity is associated with a major or decisive battle that is central to its history, role, or significance.
-
C.
hasOpposingSide
Indicates that one entity possesses or is associated with another entity that lies on the opposite or facing side relative to a reference orientation or boundary.
-
D.
hasKeyAdversary
Indicates that an entity has a primary or significant opposing force or rival that actively works against it.
-
E.
associatedOpponent
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
- 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4 p.m.