Triple
T28782922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gopchik |
E726722
|
entity |
| Predicate | placeOfFictionalWork |
P149210
|
FINISHED |
| Object | Soviet labor camp in the 1950s |
—
|
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: Soviet labor camp in the 1950s | Statement: [Gopchik, placeOfFictionalWork, Soviet labor camp in the 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfFictionalWork Context triple: [Gopchik, placeOfFictionalWork, Soviet labor camp in the 1950s]
-
A.
placeOfFictionalActivity
Indicates the location or setting where a fictional event, action, or storyline takes place.
-
B.
basedInFictionalWorkLocation
Indicates that an entity’s location or setting is situated within a fictional place as depicted in a specific creative work.
-
C.
placeOfFictionalEvent
chosen
Indicates the location where a fictional event is depicted as occurring within a narrative or story.
-
D.
worksAtFictionalPlace
Indicates that an entity is employed at or associated with performing work in a fictional or imaginary location.
-
E.
basedInFictionalLocation
Indicates that an entity’s primary setting, origin, or operations occur in a fictional (non-real) location.
- 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_69f0319aabec81908368720196f69a35 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 28, 2026, 6:20 a.m.