Triple
T256094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Narvik |
E5439
|
entity |
| Predicate | landPhase |
P5784
|
FINISHED |
| Object | Allied ground offensive around Narvik |
—
|
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: Allied ground offensive around Narvik | Statement: [Battle of Narvik, landPhase, Allied ground offensive around Narvik]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landPhase Context triple: [Battle of Narvik, landPhase, Allied ground offensive around Narvik]
-
A.
landlocked
Indicates that a place has no direct access to the open sea or ocean, being entirely surrounded by land or enclosed bodies of water.
-
B.
ground
Indicates that one entity is in contact with or supported by the ground or a ground-like surface.
-
C.
phase
chosen
Indicates that one entity is in a particular stage, step, or phase within a process, sequence, or lifecycle relative to another reference.
-
D.
lays
Indicates that one entity deposits or places something, typically eggs or objects, onto a surface or in a location.
-
E.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
- 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25d5669008190978bbd7308be11f7 |
completed | Feb. 28, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69a25b694c08819085bb4b256fa7736f |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.