Triple
T24856377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Príncipe de Asturias |
E622039
|
entity |
| Predicate | navalEngagementOpponent |
P72629
|
FINISHED |
| Object | Royal Navy at Battle of Trafalgar |
—
|
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: Royal Navy at Battle of Trafalgar | Statement: [Príncipe de Asturias, navalEngagementOpponent, Royal Navy at Battle of Trafalgar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalEngagementOpponent Context triple: [Príncipe de Asturias, navalEngagementOpponent, Royal Navy at Battle of Trafalgar]
-
A.
engagedEnemyShips
Indicates that one or more entities have actively attacked, exchanged fire with, or otherwise entered into direct combat with enemy ships.
-
B.
finalEngagementOpponentShip
Indicates that a ship is the opposing vessel faced in the final engagement or battle.
-
C.
navalEngagementType
Indicates the specific kind or category of naval combat or maritime military engagement involved in the relationship.
-
D.
opponentFleet
Indicates that one fleet is in an adversarial or opposing relationship to another fleet.
-
E.
navalOpposition
chosen
Indicates a relationship where one party actively resists, confronts, or acts against another using naval or maritime military forces.
- 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_69e2fac350d08190b3affde1b451a8c5 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:21 a.m.