Triple
T35050924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Battle of Hoover Dam |
E1011326
|
entity |
| Predicate | firstBattlePredecessor |
—
|
GENERATED |
| Object | First Battle of Hoover Dam |
—
|
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: firstBattlePredecessor Context triple: [Second Battle of Hoover Dam, firstBattlePredecessor, First Battle of Hoover Dam]
-
A.
firstFight
chosen
Indicates that the referenced event is the initial instance in which the involved entities engaged in a fight or combat with each other.
-
B.
yearOfFirstBattle
Indicates the specific year in which the first battle involving the given entities took place.
-
C.
isFirstMajorBattleOf
Indicates that a battle is the earliest significant or primary large-scale engagement within a particular war, campaign, or conflict.
-
D.
predecessorFaction
Indicates that one faction historically preceded and was replaced or succeeded by another faction.
-
E.
battleWasPartOf
Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.