Triple
T5105528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Ilovaisk |
E115082
|
entity |
| Predicate | dateOfMajorBreakthrough |
P26212
|
FINISHED |
| Object | 2014-08-24 |
—
|
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: 2014-08-24 | Statement: [Battle of Ilovaisk, dateOfMajorBreakthrough, 2014-08-24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfMajorBreakthrough Context triple: [Battle of Ilovaisk, dateOfMajorBreakthrough, 2014-08-24]
-
A.
dateOfBreakthrough
chosen
Indicates the specific date on which a significant breakthrough or major advance occurred.
-
B.
groundbreakingDate
Indicates the date on which construction officially began for a building, structure, or project (i.e., when ground was first broken).
-
C.
discoveryDate
Indicates the date on which something was first discovered or identified.
-
D.
notableEventDate
Indicates the date on which a notable or significant event associated with the subject occurred.
-
E.
markedBreakthroughOf
Indicates that an event, action, or development signified a major breakthrough or turning point for something.
- 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_69bd4440b3348190be1251fd8b7951f1 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7589e40c8190a46e4a1b7142be14 |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715e06808190931934dc9930f997 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:41 p.m.