Triple
T35311986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memphis and Charleston Railroad |
E1019795
|
entity |
| Predicate | battlesOccurredAlong |
P37770
|
FINISHED |
| Object | Battle of Corinth |
—
|
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 Corinth | Statement: [Memphis and Charleston Railroad, battlesOccurredAlong, Battle of Corinth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battlesOccurredAlong Context triple: [Memphis and Charleston Railroad, battlesOccurredAlong, Battle of Corinth]
-
A.
battleOccurredNear
chosen
Indicates that a battle took place in spatial proximity to a specified location or entity.
-
B.
battleOccurredOn
Indicates that a specific battle took place at or on a particular location or date.
-
C.
battlesWith
Indicates that two entities are engaged in active conflict, combat, or struggle against each other.
-
D.
battleBelligerentAtSite
Indicates that a particular belligerent (participant in a battle) was present and engaged in that battle at a specified site or location.
-
E.
hasSignificantBattle
Indicates that a major or decisive battle occurred involving the related entities.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7905842808190a4fc9917f0f4b60d |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.