Triple

T29471504
Position Surface form Disambiguated ID Type / Status
Subject The Zone (Stalker) E747517 entity
Predicate rulesWithinFiction P167215 FINISHED
Object path must not be walked directly 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: path must not be walked directly | Statement: [The Zone (Stalker), rulesWithinFiction, path must not be walked directly]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: rulesWithinFiction
Context triple: [The Zone (Stalker), rulesWithinFiction, path must not be walked directly]
  • A. eraWithinFiction
    Indicates that a time period or era exists inside the narrative world or timeline of a fictional work.
  • B. showWithinFiction
    Indicates that one entity is depicted, referenced, or occurs as part of the fictional world or narrative context of another entity.
  • C. guardedByInFiction
    Indicates that one fictional entity is protected or watched over by another within a narrative context.
  • D. worksInFictionalContext
    Indicates that an entity performs work or fulfills a role within a fictional or imagined setting rather than in real-world circumstances.
  • E. conductsInFiction
    Indicates that an entity carries out or performs an action or role within a fictional context or narrative.
  • F. None of above. chosen

Provenance (4 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_69f0bd42cf308190bb01b20bc5b7c2d0 completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69f66babf5e08190b8e1007546f3881a completed May 2, 2026, 9:25 p.m.
PD Predicate disambiguation batch_69f66339175c819080bd70f0ff7057b1 completed May 2, 2026, 8:48 p.m.
PDg Predicate description generation batch_69f663ff176c8190aaadb475f75daee4 completed May 2, 2026, 8:52 p.m.
Created at: April 28, 2026, 3:57 p.m.