Triple
T1190183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Vicksburg |
E25339
|
entity |
| Predicate | dateOfMajorTurningPoint |
P925
|
FINISHED |
| Object | 1863-05-22 |
—
|
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: 1863-05-22 | Statement: [Siege of Vicksburg, dateOfMajorTurningPoint, 1863-05-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfMajorTurningPoint Context triple: [Siege of Vicksburg, dateOfMajorTurningPoint, 1863-05-22]
-
A.
notableEventDate
chosen
Indicates the date on which a notable or significant event associated with the subject occurred.
-
B.
movementDate
Indicates the date on which a movement, transfer, or relocation event occurs.
-
C.
dateSignificance
Indicates the specific importance, meaning, or notable role that a particular date holds within a given context or relationship.
-
D.
timePeriodOfMajorImportance
Indicates that a particular time period holds significant importance or prominence within a given context or domain.
-
E.
turningPointIn
Indicates that an event or situation serves as a decisive change or pivotal moment within a larger process, narrative, or development.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd58d8d88190b8d9c9c9de7f4e97 |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5bacc481909e8dfd5215e4711a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.