Triple
T7172438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. 1st Army |
E167231
|
entity |
| Predicate | WWIIOperation |
P72293
|
FINISHED |
| Object | invasion of Normandy |
—
|
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: invasion of Normandy | Statement: [U.S. 1st Army, WWIIOperation, invasion of Normandy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: WWIIOperation Context triple: [U.S. 1st Army, WWIIOperation, invasion of Normandy]
-
A.
WWIITheater
Indicates the geographic or operational theater in which a World War II-related event, action, or entity was involved.
-
B.
SovietOperation
Indicates that an operation, mission, or organized activity is conducted by, on behalf of, or under the authority of the Soviet Union or its institutions.
-
C.
militaryOperationName
chosen
Indicates the specific named military operation associated with an action, event, or entity.
-
D.
WWIIEvent
Indicates that the event is part of, or directly related to, the historical period and activities of World War II.
-
E.
majorLiberationOperation
Indicates a large-scale, coordinated military or strategic action aimed at freeing a territory, population, or group from control, occupation, or oppression.
- 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_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. |
Created at: March 27, 2026, 2:48 p.m.