Triple
T2580073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Gulag Archipelago |
E57067
|
entity |
| Predicate | publicationHistory |
P26025
|
FINISHED |
| Object | first published in the West |
—
|
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: first published in the West | Statement: [The Gulag Archipelago, publicationHistory, first published in the West]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicationHistory Context triple: [The Gulag Archipelago, publicationHistory, first published in the West]
-
A.
hasPublisherHistory
chosen
Indicates that there exists a record of past or current publishing relationships associated with the entity.
-
B.
historicalPaper
Indicates that a paper has significant historical importance or impact within its field or context.
-
C.
publishedAs
Indicates that an entity is released, issued, or made publicly available under a particular name, format, or identity.
-
D.
publicationAbout
Indicates that a publication has content whose subject or focus is the referenced entity.
-
E.
formerPublication
Indicates that an entity was previously published in, or associated as a publication with, another entity but is no longer currently so.
- 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3a9fd3c8190a521931e40cd801c |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0cfeae08190aed03866ba071c5c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.