Triple
T38617441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Britannia (1682) |
E936770
|
entity |
| Predicate | primaryOpponentNavy |
P72629
|
FINISHED |
| Object | French Navy |
E9310
|
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: French Navy | Statement: [HMS Britannia (1682), primaryOpponentNavy, French Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryOpponentNavy Context triple: [HMS Britannia (1682), primaryOpponentNavy, French Navy]
-
A.
primaryOpposingCommanderUS
Indicates that the referenced person is the main opposing military commander of the United States in a given conflict or operation.
-
B.
opponentFleet
Indicates that one fleet is in an adversarial or opposing relationship to another fleet.
-
C.
navalOpposition
chosen
Indicates a relationship where one party actively resists, confronts, or acts against another using naval or maritime military forces.
-
D.
primaryOpponentOfUSSConstitution
Indicates that one entity served as the main adversary or opposing force to the USS Constitution in a specific conflict or context.
-
E.
previousNavy
Indicates that one entity previously served in, belonged to, or was part of a navy before the current point in time.
- 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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41f448e4f08190b85f99a94c6d87cf |
completed | June 29, 2026, 4:27 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.