Triple
T20855198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Markale market shellings |
E513461
|
entity |
| Predicate | secondAttackDate |
P142122
|
FINISHED |
| Object | 1995-08-28 |
—
|
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: 1995-08-28 | Statement: [Markale market shellings, secondAttackDate, 1995-08-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondAttackDate Context triple: [Markale market shellings, secondAttackDate, 1995-08-28]
-
A.
secondReachedDate
Indicates the date on which the second specified event, state, or condition is reached or occurs.
-
B.
secondApparitionDate
Indicates the date on which an entity appeared or manifested for the second time.
-
C.
secondAccidentDate
Indicates the date on which a second accident involving the same subject or case occurred.
-
D.
secondPhaseStartDate
Indicates the date on which the second phase of a process, project, or activity begins.
-
E.
resultOfSecondAttack
Indicates that an event or state occurs as a consequence of a second attack in a sequence of attacks.
- 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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3a7113c819087994bcdfe643bc1 |
completed | April 21, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:44 p.m.