Triple
T24200076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General John Stark Day |
E599949
|
entity |
| Predicate | honoreeNotableBattle |
P87908
|
FINISHED |
| Object | Battle of Bennington |
—
|
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 Bennington | Statement: [General John Stark Day, honoreeNotableBattle, Battle of Bennington]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honoreeNotableBattle Context triple: [General John Stark Day, honoreeNotableBattle, Battle of Bennington]
-
A.
notableBattleRecognized
Indicates that a particular battle is formally acknowledged or recognized as notable in relation to the subject.
-
B.
refersToPersonNotableBattle
chosen
Indicates that a person is associated with or identified by a specific notable battle in which they played a significant role.
-
C.
notableBattlefield
Indicates that a location is recognized as the site of a historically significant battle or military engagement.
-
D.
notableBattleRole
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
E.
battleHonors
Indicates that an entity has been awarded or is associated with specific honors or distinctions earned through participation in battles or military engagements.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca08874819081dd6613ac462c40 |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:36 p.m.