Triple
T38634460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Gulag |
E937540
|
entity |
| Predicate | chronologyInCampaign |
P198097
|
FINISHED |
| Object | mid-campaign mission |
—
|
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: mid-campaign mission | Statement: [The Gulag, chronologyInCampaign, mid-campaign mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologyInCampaign Context triple: [The Gulag, chronologyInCampaign, mid-campaign mission]
-
A.
chronologyWithinConflict
Indicates that one event or time period occurs within the temporal span of a specified conflict or war.
-
B.
chronologyOf
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with another entity.
-
C.
chronologicalPositionInCampaign
chosen
Indicates the position or order of an event, action, or element within the overall sequence of a campaign.
-
D.
chronologySeries
Indicates that one entity is part of, or defines, a chronological sequence or ordered series of events or items.
-
E.
chronologyIn
Indicates that one event or temporal entity occurs within the chronological scope or timeframe defined by another.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fecb4d02f881909a9ee97ce98000d5 |
completed | May 9, 2026, 5:51 a.m. |
| PD | Predicate disambiguation | batch_69fec9846c1c8190b317f0711f0755db |
completed | May 9, 2026, 5:43 a.m. |
Created at: May 3, 2026, 4:32 p.m.