Triple
T28732349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salem Church |
E730694
|
entity |
| Predicate | battlefieldName |
P28951
|
FINISHED |
| Object | Salem Church battlefield |
—
|
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: Salem Church battlefield | Statement: [Salem Church, battlefieldName, Salem Church battlefield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battlefieldName Context triple: [Salem Church, battlefieldName, Salem Church battlefield]
-
A.
battlefieldOf
Indicates that a location is the site where a particular battle or military engagement took place.
-
B.
battleAlsoKnownAs
chosen
Indicates that a particular battle is known by an alternative name or names.
-
C.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
D.
battleTypeAtSite
Indicates the specific type or category of battle that occurred at a given site.
-
E.
battleOccurredNear
Indicates that a battle took place in spatial proximity to a specified location or 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 5:59 a.m.