Triple
T7566504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Schooneveld |
E178925
|
entity |
| Predicate | attackingSide |
P39750
|
FINISHED |
| Object | Anglo-French fleet |
—
|
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: Anglo-French fleet | Statement: [Battle of Schooneveld, attackingSide, Anglo-French fleet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackingSide Context triple: [Battle of Schooneveld, attackingSide, Anglo-French fleet]
-
A.
attackerSide
chosen
Indicates which party or faction is responsible for carrying out an attack in a conflict or violent incident.
-
B.
monarchOfAttackingSide
Indicates that the subject is the reigning monarch who leads or represents the attacking side in a conflict or confrontation.
-
C.
attackedFrom
Indicates that one entity initiated an attack against another entity originating from a specific source location or position.
-
D.
mainAttacker
Indicates that an entity is the primary or leading aggressor responsible for initiating or carrying out an attack against another entity.
-
E.
opponentCommanderSide
Indicates that one commander is positioned on the opposing side relative to another commander in a conflict or competitive scenario.
- 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_69c69f2f80288190b95cceb4da92ab2b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8fde87c81909795fc713d7378ff |
completed | March 27, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69c6f4dc485c819080da13e3b7f4f08f |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:50 p.m.