Triple
T25711103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Yser |
E644730
|
entity |
| Predicate | defensiveLineCreated |
P164178
|
FINISHED |
| Object | Yser Front |
—
|
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: Yser Front | Statement: [Battle of the Yser, defensiveLineCreated, Yser Front]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defensiveLineCreated Context triple: [Battle of the Yser, defensiveLineCreated, Yser Front]
-
A.
defensiveLineAlong
Indicates a spatial relationship where a defensive formation or barrier is arranged along the length or path of a specified line or boundary.
-
B.
usedDefensiveLine
Indicates that an entity employed or deployed a particular defensive line as part of its strategy or actions.
-
C.
defensiveLineCharacteristic
Indicates a characteristic or attribute that describes the nature, style, or qualities of a defensive line in a competitive or strategic context.
-
D.
defensiveLineTargeted
Indicates that a specific defensive line or its players are the intended focus of an offensive play, strategy, or action.
-
E.
primaryDefensiveLine
Indicates the main line of defense that first engages or protects against an opposing force or threat.
- F. None of above. chosen
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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f643c204508190a43fe0ec5165b01c |
completed | May 2, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f6430975b481909191219ad13ef77e |
completed | May 2, 2026, 6:31 p.m. |
Created at: April 21, 2026, 9:14 p.m.