Triple

T35156594
Position Surface form Disambiguated ID Type / Status
Subject Wild at Heart E1015138 entity
Predicate workLocationOfFictionalFamily P76778 FINISHED
Object Wildlife game reserve 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: Wildlife game reserve | Statement: [Wild at Heart, workLocationOfFictionalFamily, Wildlife game reserve]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: workLocationOfFictionalFamily
Context triple: [Wild at Heart, workLocationOfFictionalFamily, Wildlife game reserve]
  • A. workLocationOfFictionalCharacter chosen
    Indicates the place or organization where a fictional character is depicted as working within their narrative context.
  • B. settingOfFictionalResidence
    Indicates that a location serves as the setting or backdrop for a fictional residence within a narrative work.
  • C. frequentedByFictionalFamily
    Indicates that a place or establishment is regularly visited or commonly associated with a particular fictional family.
  • D. stateOfFictionalResidence
    Indicates the state or region in which a fictional character’s residence is located.
  • E. fictionalResidence
    Indicates that one entity is the place where another entity lives or is based within a fictional or imaginary context.
  • 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_69f76ddb3a708190b521ba2970b17178 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78cf278648190896f49cd4c077520 completed May 3, 2026, 5:59 p.m.
PD Predicate disambiguation batch_69f78b9106008190930b3b3675b737d6 completed May 3, 2026, 5:53 p.m.
Created at: May 3, 2026, 4:02 p.m.