Triple
T5820493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bucentaure |
E129093
|
entity |
| Predicate | primaryOpponentFleet |
P53687
|
FINISHED |
| Object | British fleet at Trafalgar |
—
|
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: British fleet at Trafalgar | Statement: [Bucentaure, primaryOpponentFleet, British fleet at Trafalgar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryOpponentFleet Context triple: [Bucentaure, primaryOpponentFleet, British fleet at Trafalgar]
-
A.
opponentFleet
chosen
Indicates that one fleet is in an adversarial or opposing relationship to another fleet.
-
B.
primaryEnemyForces
Indicates that the related entities constitute the main opposing or hostile forces in a conflict or competitive situation.
-
C.
primaryAntagonistShip
Indicates that one ship serves as the main opposing or enemy vessel in relation to another entity or context.
-
D.
navalFleet
Indicates a relationship where multiple naval vessels are organized and operate together as a coordinated maritime military force.
-
E.
navalForceInvolved
Indicates that a naval military force participates in, contributes to, or is otherwise involved in a specified event or operation.
- 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_69c0084869e881908d7859492183ca7b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0333fdd7081908d829265caa2ac11 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:53 p.m.