Triple
T9153126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chibi (Red Cliff) historical area |
E219637
|
entity |
| Predicate | battleCommemoratedDate |
P828
|
FINISHED |
| Object | winter of 208–209 CE |
—
|
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: winter of 208–209 CE | Statement: [Chibi (Red Cliff) historical area, battleCommemoratedDate, winter of 208–209 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleCommemoratedDate Context triple: [Chibi (Red Cliff) historical area, battleCommemoratedDate, winter of 208–209 CE]
-
A.
commemoratedOn
Indicates that something is remembered, honored, or celebrated on a specific date or occasion.
-
B.
commemorationDate
chosen
Indicates the date on which an event, person, or occasion is formally remembered or honored.
-
C.
commemoratedSince
Indicates that a commemoration of one entity for another has been in effect starting from a specific point in time.
-
D.
firstOfficialCommemorationDate
Indicates the calendar date on which something was formally and officially commemorated for the first time.
-
E.
timeOfEventCommemorated
Indicates the specific time or date at which the event being commemorated originally occurred.
- 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_69ca83e25418819093c6503deeaf30de |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca96e323881909cbf4d6708f24f79 |
completed | April 1, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69cc6603ce8c8190bf6e8d6754bdec54 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:20 p.m.