Triple
T25711085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Yser |
E644730
|
entity |
| Predicate | objectiveOfBelgium |
P159798
|
FINISHED |
| Object | prevent German access to Dunkirk and Calais |
—
|
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: prevent German access to Dunkirk and Calais | Statement: [Battle of the Yser, objectiveOfBelgium, prevent German access to Dunkirk and Calais]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectiveOfBelgium Context triple: [Battle of the Yser, objectiveOfBelgium, prevent German access to Dunkirk and Calais]
-
A.
objectiveOfBelgium
chosen
Indicates that something is the goal, aim, or strategic objective pursued by Belgium.
-
B.
strategicGoalOfDutch
Indicates that something represents or contributes to the strategic goals or long-term objectives defined by Dutch entities or authorities.
-
C.
positionInBelgium
Indicates that one entity occupies a specific geographic location within the territory of Belgium.
-
D.
objectiveOfFrance
Indicates that something is an objective, goal, or aim pursued by France.
-
E.
otherRegionsOfBelgium
Indicates that the related entities are regions of Belgium that are distinct from a specified primary Belgian region.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f600c18a14819081b5914dd3b0f9cf |
completed | May 2, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 9:14 p.m.