Triple
T3932434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German 352nd Infantry Division |
E90824
|
entity |
| Predicate | roleOnDday |
P268
|
FINISHED |
| Object | defense of Omaha Beach |
—
|
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: defense of Omaha Beach | Statement: [German 352nd Infantry Division, roleOnDday, defense of Omaha Beach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOnDday Context triple: [German 352nd Infantry Division, roleOnDday, defense of Omaha Beach]
-
A.
roleInCalendar
Indicates that an entity holds a specific role or function within the context of a particular calendar or scheduled event.
-
B.
role
chosen
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
C.
plannedRole
Indicates that an entity is expected or intended to assume a particular role or function in a planned or future context.
-
D.
roleAtMidway
Indicates that an entity holds or held a specific role, position, or function at the midpoint or intermediate stage of a process, event, or time period.
-
E.
servesRole
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
- 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_69aed95f26e0819094b0e71974543a19 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeedaaf3c881909539831bf3a8bf10 |
completed | March 9, 2026, 3:56 p.m. |
| PD | Predicate disambiguation | batch_69aee7625ad4819097e4e8a168c19274 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:23 p.m.