Triple
T38481853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Witchcraft |
E915697
|
entity |
| Predicate | setDuringFictionalTime |
P60994
|
FINISHED |
| Object | Cold War |
—
|
NE NERFINISHED |
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: Cold War | Statement: [Operation Witchcraft, setDuringFictionalTime, Cold War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setDuringFictionalTime Context triple: [Operation Witchcraft, setDuringFictionalTime, Cold War]
-
A.
setInFictionalYear
Indicates that the events or narrative of a work are situated in a specified fictional or non-real calendar year.
-
B.
fictionalTime
chosen
Indicates that the associated time or temporal reference exists only within a fictional or imagined context, rather than in real-world chronology.
-
C.
hasFictionalTimeAfter
Indicates that one fictional time point or period occurs later than another within a narrative or imagined timeline.
-
D.
timeTravelExperimentDateInStory
Indicates the date on which a time travel experiment occurs within the narrative timeline of the story.
-
E.
setInFictionalLocation
Indicates that an event, story, or narrative takes place within a fictional or imagined location rather than a real-world setting.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.