Triple
T15064488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS-Schwere Panzerabteilung 101 |
E379718
|
entity |
| Predicate | garrisonDuringNormandy |
P75677
|
FINISHED |
| Object | area of Caen |
—
|
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: area of Caen | Statement: [SS-Schwere Panzerabteilung 101, garrisonDuringNormandy, area of Caen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonDuringNormandy Context triple: [SS-Schwere Panzerabteilung 101, garrisonDuringNormandy, area of Caen]
-
A.
garrisonBeforeDday
Indicates that one entity served as a military garrison for the other prior to the D-Day landings in World War II.
-
B.
garrisonedDuring
chosen
Indicates that a military force was stationed or quartered at a location for defense or control during a specified time period.
-
C.
garrisonDuringWar
Indicates that a military force is stationed in a specific location for defense or control during a time of war.
-
D.
garrisonIncluded
Indicates that a particular garrison is included within, or forms part of, a specified larger military force, unit, or installation.
-
E.
garrisonDuringBattle
Indicates that an entity is stationed to defend or hold a location specifically during the time a battle is taking place.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dedee803ac81908bb7d66e49c2eb72 |
completed | April 15, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:02 a.m.