Triple
T891305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 716th Infantry Division |
E19243
|
entity |
| Predicate | statusOnD-Day |
P19322
|
FINISHED |
| Object | understrength |
—
|
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: understrength | Statement: [716th Infantry Division, statusOnD-Day, understrength]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOnD-Day Context triple: [716th Infantry Division, statusOnD-Day, understrength]
-
A.
statusDuringPearlHarbor
Indicates the role, condition, or situation an entity held specifically during the time of the Pearl Harbor attack.
-
B.
statusDuringWar
chosen
Indicates the role, condition, or classification an entity held specifically during a period of war.
-
C.
numberOfChannelCrossingsAtNormandy
Indicates the number of times an entity crossed the English Channel specifically in relation to the Normandy area or campaign.
-
D.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
E.
laterStatus
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
- 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad019e448190ab991e85dc6d7708 |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa9372e88190b5a9db4afdc045c6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.