Triple
T5184612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vicksburg, Mississippi |
E116999
|
entity |
| Predicate | surrenderDateCivilWar |
P4667
|
FINISHED |
| Object | July 4, 1863 |
—
|
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: July 4, 1863 | Statement: [Vicksburg, Mississippi, surrenderDateCivilWar, July 4, 1863]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surrenderDateCivilWar Context triple: [Vicksburg, Mississippi, surrenderDateCivilWar, July 4, 1863]
-
A.
civilWarEnd
Indicates that an internal armed conflict within a country has come to an official or de facto conclusion.
-
B.
surrenderDate
chosen
Indicates the date on which an entity formally yields control, possession, or rights, typically ending its claim or resistance.
-
C.
emancipationProclamationDate
Indicates the date on which an emancipation proclamation was formally issued or took effect.
-
D.
surrenderedIn
Indicates that an entity yielded or gave up control, power, or resistance within a specific event, context, or situation.
-
E.
surrenderYear
Indicates the year in which an entity formally surrendered, ending its resistance or hostilities.
- 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_69bd44620ff48190bcac01782107a397 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c1354c81908176703b4853c1a4 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b7e8b4819092ec3965e11f2dea |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:46 p.m.