Triple

T26533114
Position Surface form Disambiguated ID Type / Status
Subject Sanford and Son junkyard E670872 entity
Predicate hasStructureInFiction P106216 FINISHED
Object office 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: office | Statement: [Sanford and Son junkyard, hasStructureInFiction, office]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasStructureInFiction
Context triple: [Sanford and Son junkyard, hasStructureInFiction, office]
  • A. hasFormatInFiction
    Indicates that a work of fiction is presented or realized in a particular narrative or media format (e.g., novel, film, comic).
  • B. hasFeatureInFiction chosen
    Indicates that a fictional work includes or portrays a particular feature, trait, or characteristic.
  • C. hasFictionComponent
    Indicates that something includes, contains, or is composed in part of a fictional element or work.
  • D. commandStructureInFiction
    Indicates a hierarchical command or authority relationship that exists between characters or groups within a fictional setting.
  • E. hasDramaticStructure
    Indicates that something possesses or follows a specific dramatic structure, such as an organized sequence of narrative or theatrical elements (e.g., exposition, climax, resolution).
  • 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_69eeb31ea1e08190b9ff43cf9bc25bf8 completed April 27, 2026, 12:51 a.m.
NER Named-entity recognition batch_69f74c70fd248190a9d5543afcb08211 completed May 3, 2026, 1:24 p.m.
PD Predicate disambiguation batch_69f7478e3b548190a51d5d436e2bb036 completed May 3, 2026, 1:03 p.m.
Created at: April 27, 2026, 1:37 a.m.