Triple
T9177612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Creek War (1813–1814) |
E220239
|
entity |
| Predicate | dateOfBattleOfHorseshoeBend |
P86672
|
FINISHED |
| Object | 1814-03-27 |
—
|
LITERAL FINISHED |
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: 1814-03-27 | Statement: [Creek War (1813–1814), dateOfBattleOfHorseshoeBend, 1814-03-27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfBattleOfHorseshoeBend Context triple: [Creek War (1813–1814), dateOfBattleOfHorseshoeBend, 1814-03-27]
-
A.
dateOfBattleOfKingsMountain
Indicates the calendar date on which the Battle of Kings Mountain took place.
-
B.
dateOfSouthernAssault
Indicates the specific date on which a southern-initiated assault or attack took place.
-
C.
battleOccurredOn
Indicates that a specific battle took place at or on a particular location or date.
-
D.
BattleOfEniwetokDate
Indicates the specific calendar date on which the Battle of Eniwetok took place.
-
E.
dateOfConfederateCommission
Indicates the date on which an individual or entity was officially commissioned or appointed by the Confederate authorities.
- F. None of above. chosen
Provenance (4 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccbfa60c3c8190b6335b9067de5b72 |
completed | April 1, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc66d7bf648190b8bff5b584b84975 |
completed | April 1, 2026, 12:29 a.m. |
Created at: March 30, 2026, 7:23 p.m.