Triple
T11156772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 80th Infantry Division |
E263929
|
entity |
| Predicate | enteredCombatInTheater |
P38978
|
FINISHED |
| Object | August 1944 |
—
|
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: August 1944 | Statement: [80th Infantry Division, enteredCombatInTheater, August 1944]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredCombatInTheater Context triple: [80th Infantry Division, enteredCombatInTheater, August 1944]
-
A.
combatRelated
Indicates that the entities are connected through participation in, involvement with, or direct association to combat or military conflict.
-
B.
sawCombat
chosen
Indicates that an entity directly participated in active military or armed conflict.
-
C.
militaryTheater
Indicates that an entity is a geographic or operational area where military operations or campaigns are conducted.
-
D.
firstCombatOperation
Indicates that the referenced combat operation is the earliest or initial combat action undertaken by the entity in question.
-
E.
enteredCombatInEurope
Indicates that an entity became actively involved in military combat operations within the geographical region of Europe.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8741cd48190b7cc29c6b6bc54ff |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cec26fc8190a5497d186306f935 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.