Triple
T32091583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German 243rd Infantry Division |
E819607
|
entity |
| Predicate | statusOnDDay |
P53679
|
FINISHED |
| Object | on coastal defense duty in 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: on coastal defense duty in Normandy | Statement: [German 243rd Infantry Division, statusOnDDay, on coastal defense duty in Normandy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOnDDay Context triple: [German 243rd Infantry Division, statusOnDDay, on coastal defense duty in Normandy]
-
A.
statusAtDay
chosen
Indicates the specific status or condition an entity has on a given calendar day.
-
B.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
C.
statusDetermines
Indicates that the status or condition of one entity determines or governs the state, outcome, or behavior of another entity.
-
D.
statusPeriod
Indicates the time interval during which a particular status or condition is in effect.
-
E.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
- 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: May 1, 2026, 12:25 a.m.