Triple
T26239049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Holly Springs |
E656256
|
entity |
| Predicate | railLineTargeted |
P84464
|
FINISHED |
| Object | Mississippi Central Railroad |
—
|
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: Mississippi Central Railroad | Statement: [Battle of Holly Springs, railLineTargeted, Mississippi Central Railroad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railLineTargeted Context triple: [Battle of Holly Springs, railLineTargeted, Mississippi Central Railroad]
-
A.
railwayTargeted
chosen
Indicates that a railway or rail-related infrastructure is deliberately chosen and attacked as a target.
-
B.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
C.
railLineOrigin
Indicates that a rail line begins or originates from a specified location or point.
-
D.
railwayLineNow
Indicates that a previously existing railway line has been replaced, succeeded, or is currently represented by a new or different railway line.
-
E.
railwayLineRole
Indicates the specific functional role or purpose that a railway line serves within a rail network or transportation system.
- 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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60d8d749881909594e450462bca49 |
completed | May 2, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 9:03 p.m.