Triple
T12731284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 33rd Infantry Division |
E304241
|
entity |
| Predicate | successorUnitType |
P60459
|
FINISHED |
| Object | Panzer division |
—
|
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: Panzer division | Statement: [33rd Infantry Division, successorUnitType, Panzer division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorUnitType Context triple: [33rd Infantry Division, successorUnitType, Panzer division]
-
A.
successorUnitIntegratedInto
Indicates that a subsequent or replacement unit has been incorporated into, or merged with, another unit as part of an organizational or structural succession.
-
B.
successorType
chosen
Indicates the specific kind or category of successor relationship that holds between one entity and the next in a sequence or hierarchy.
-
C.
successorSubunit
Indicates that one organizational subunit is the direct successor or continuation of another subunit in a structural or temporal sequence.
-
D.
successorRegimeType
Indicates the type or form of government or regime that directly follows and replaces a preceding regime.
-
E.
successorSystem
Indicates that one system directly follows and replaces another in function, role, or version.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:25 p.m.