Triple
T34057004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Confederate Heartland Offensive |
E873387
|
entity |
| Predicate | campaignIncludes |
P178401
|
FINISHED |
| Object | Battle of Perryville |
—
|
NE NERFINISHED |
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: Battle of Perryville | Statement: [Confederate Heartland Offensive, campaignIncludes, Battle of Perryville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campaignIncludes Context triple: [Confederate Heartland Offensive, campaignIncludes, Battle of Perryville]
-
A.
promotionIncludes
Indicates that a particular promotion encompasses, covers, or applies to a specified item, service, or condition.
-
B.
productIncludes
Indicates that a product contains, comprises, or is composed of the specified component, item, or feature.
-
C.
distributionIncludes
Indicates that a distribution or release of something contains or encompasses the specified item or component.
-
D.
packagingIncludes
Indicates that the packaging of one item contains or comes with another specified item or component.
-
E.
orderIncludes
Indicates that a particular order contains or comprises the specified item(s) or component(s).
- F. None of above. chosen
Provenance (4 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_69f349a3ec2c8190b62da76e54231a0f |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7107acf0481909b01467b9ebbde01 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fb41a9c8190a121e62e510dc18a |
completed | May 3, 2026, 9:04 a.m. |
Created at: May 1, 2026, 1:52 a.m.