Triple
T7172439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. 1st Army |
E167231
|
entity |
| Predicate | WWIIAdvanceDirection |
P74528
|
FINISHED |
| Object | from Normandy into Germany |
—
|
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: from Normandy into Germany | Statement: [U.S. 1st Army, WWIIAdvanceDirection, from Normandy into Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: WWIIAdvanceDirection Context triple: [U.S. 1st Army, WWIIAdvanceDirection, from Normandy into Germany]
-
A.
WWIITheater
Indicates the geographic or operational theater in which a World War II-related event, action, or entity was involved.
-
B.
higherCommandDuringWWII
Indicates that one entity served as the superior military authority or command over another entity during World War II.
-
C.
WWIIEvent
Indicates that the event is part of, or directly related to, the historical period and activities of World War II.
-
D.
sideInWorldWarII
Indicates that an entity was aligned with or participated on a particular side during World War II.
-
E.
WWIIUse
Indicates that one entity made use of another entity during World War II, typically for military, strategic, or wartime-related purposes.
- 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_69c68889a2748190a316c5e65360361a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e88b0a448190a19bd2d9e2a310a4 |
completed | March 27, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69c6e1ce5f048190808c378a980f7bb6 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e24af9ac8190b24eee206ba8be36 |
completed | March 27, 2026, 8:02 p.m. |
Created at: March 27, 2026, 2:48 p.m.