Triple
T9065228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinjar |
E217227
|
entity |
| Predicate | recaptureTime |
P56190
|
FINISHED |
| Object | November 2015 |
—
|
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: November 2015 | Statement: [Sinjar, recaptureTime, November 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recaptureTime Context triple: [Sinjar, recaptureTime, November 2015]
-
A.
recaptureDate
chosen
Indicates the date on which something that was previously captured or held is captured or taken back again.
-
B.
capturedAt
Indicates the specific time or moment at which an entity was captured, recorded, or taken.
-
C.
peakRecaptured
Indicates that a previously lost or diminished peak value, level, or intensity has been regained or reached again.
-
D.
wasRecapturedBy
Indicates that an entity which had previously escaped or been released was caught again by another entity.
-
E.
recaptureContext
Indicates that a previously established context or situation is being regained or restored after it was lost, interrupted, or diminished.
- 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_69ca83d5a7f48190b16c1e59bd43ede0 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc94bc91d48190acf62afa90eec079 |
completed | April 1, 2026, 3:45 a.m. |
| PD | Predicate disambiguation | batch_69cc65f881248190bfd220bb28a9fb5f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:11 p.m.