Triple
T30966804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Fishguard |
E788981
|
entity |
| Predicate | invasionType |
P113615
|
FINISHED |
| Object | amphibious landing |
—
|
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: amphibious landing | Statement: [Battle of Fishguard, invasionType, amphibious landing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invasionType Context triple: [Battle of Fishguard, invasionType, amphibious landing]
-
A.
methodOfInvasion
chosen
Indicates the specific way or technique by which an invasion is carried out.
-
B.
invasionCodename
Indicates the codename assigned to a specific military invasion operation.
-
C.
invade
Indicates entering another entity’s territory or domain, typically by force or without permission, in order to take control or exert dominance.
-
D.
invasionAddressed
Indicates that an invasion event has been responded to or dealt with through some form of action, intervention, or resolution.
-
E.
typeOfConquest
Indicates the specific manner or category of conquest by which one entity gains control over or dominance of another.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:54 p.m.