Triple
T34600668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 118th Field Artillery Regiment |
E888451
|
entity |
| Predicate | hasPredecessorUnit |
—
|
GENERATED |
| Object | Georgia artillery militia units |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPredecessorUnit Context triple: [118th Field Artillery Regiment, hasPredecessorUnit, Georgia artillery militia units]
-
A.
predecessorUnit
chosen
Indicates that one unit directly precedes another in an ordered sequence or hierarchy.
-
B.
hasPredecessorMP
Indicates that one member of parliament previously held the same parliamentary position or seat before another member of parliament.
-
C.
hasPredecessorStructureFrom
Indicates that one structure existed or was established before another structure in a sequential or developmental order.
-
D.
hasPredecessorBand
Indicates that a band is preceded by another band, identifying the earlier band in a succession or lineage of bands.
-
E.
hasPredecessorType
Indicates that one type is derived from, follows, or is based on another earlier or more fundamental type in a sequence or hierarchy.
- F. None of above.
Provenance (1 batch)
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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:03 a.m.