Triple
T33467085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 18th Panzer Division |
E857081
|
entity |
| Predicate | yearOfFirstCombat |
P25493
|
FINISHED |
| Object | 1941 |
—
|
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: 1941 | Statement: [18th Panzer Division, yearOfFirstCombat, 1941]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfFirstCombat Context triple: [18th Panzer Division, yearOfFirstCombat, 1941]
-
A.
yearOfFirstBattle
chosen
Indicates the specific year in which the first battle involving the given entities took place.
-
B.
yearOfBattle
Indicates the specific calendar year in which a particular battle took place.
-
C.
firstCombatUseDate
Indicates the date on which something (typically a weapon, system, or tactic) was first used in actual combat.
-
D.
firstCombatOperation
Indicates that the referenced combat operation is the earliest or initial combat action undertaken by the entity in question.
-
E.
conflictBeganInYear
Indicates that the specified conflict started or first broke out in the given calendar year.
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: May 1, 2026, 1:37 a.m.