Triple
T34413770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Utoy Creek |
E883344
|
entity |
| Predicate | railTarget |
P84464
|
FINISHED |
| Object | Atlanta and West Point 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: Atlanta and West Point Railroad | Statement: [Battle of Utoy Creek, railTarget, Atlanta and West Point Railroad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railTarget Context triple: [Battle of Utoy Creek, railTarget, Atlanta and West Point Railroad]
-
A.
railwayTargeted
chosen
Indicates that a railway or rail-related infrastructure is deliberately chosen and attacked as a target.
-
B.
railHead
Indicates a relationship where one location serves as the terminus or primary endpoint of a railway line for another location or transport link.
-
C.
rail
Indicates that one entity criticizes, scolds, or complains vehemently about another entity or situation.
-
D.
railTracks
Indicates that one entity consists of, includes, or is associated with rail tracks used for guiding trains or rail vehicles.
-
E.
coordinatesRailTrafficWith
Indicates that one entity organizes and synchronizes rail operations or movements with another entity to ensure coordinated train traffic.
- 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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71947ad88819082ab9d85dd493b01 |
completed | May 3, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.