Triple
T34052798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosebud Battlefield |
E873267
|
entity |
| Predicate | battleEffect |
P100772
|
FINISHED |
| Object | forced Crook to withdraw to his base on Goose Creek |
—
|
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: forced Crook to withdraw to his base on Goose Creek | Statement: [Rosebud Battlefield, battleEffect, forced Crook to withdraw to his base on Goose Creek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleEffect Context triple: [Rosebud Battlefield, battleEffect, forced Crook to withdraw to his base on Goose Creek]
-
A.
battleSystem
Indicates a relationship where entities are engaged in or governed by a structured combat or conflict-resolution mechanism.
-
B.
battleTarget
Indicates that one entity is the chosen opponent or objective that another entity is engaging or intends to engage in battle.
-
C.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
D.
attackEffect
chosen
Indicates that one entity’s attack produces a specific effect or consequence on another entity.
-
E.
resultOfBattle
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
- 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_69f349a3ec2c8190b62da76e54231a0f |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:52 a.m.