Triple
T26493810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turner’s Gap |
E669225
|
entity |
| Predicate | nearestLargeBattle |
P70569
|
FINISHED |
| Object | Battle of Antietam |
—
|
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 Antietam | Statement: [Turner’s Gap, nearestLargeBattle, Battle of Antietam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestLargeBattle Context triple: [Turner’s Gap, nearestLargeBattle, Battle of Antietam]
-
A.
battleWasPartOf
Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
-
B.
ключевоеСражение
Indicates a battle that is decisive or pivotal in determining the outcome of a larger conflict or war.
-
C.
isLargestBattleIn
Indicates that a battle is the largest (by scale, size, or impact) among all battles occurring within a specified context, such as a war, campaign, region, or time period.
-
D.
numberOfMajorBattles
Indicates the total count of significant or major battles associated with an entity or event.
-
E.
notableBattlefield
chosen
Indicates that a location is recognized as the site of a historically significant battle or military engagement.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 1:06 a.m.