Triple

T983863
Position Surface form Disambiguated ID Type / Status
Subject New York Street backlot set E21234 entity
Predicate typicallyLocatedAt P40 FINISHED
Object major film studio backlot 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: major film studio backlot | Statement: [New York Street backlot set, typicallyLocatedAt, major film studio backlot]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicallyLocatedAt
Context triple: [New York Street backlot set, typicallyLocatedAt, major film studio backlot]
  • A. locatedIn chosen
    Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
  • B. locatedAlong
    Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
  • C. locatedUnder
    Indicates that one entity is positioned directly or generally beneath another entity in space.
  • D. agencyLocatedIn
    Indicates that an agency is situated or based within a specific geographic or administrative location.
  • E. locatedOff
    Indicates that one entity is situated away from, but in the vicinity of, another entity or reference point, rather than directly on or within it.
  • 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_69a493c383dc8190a03257f22d4b4183 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b493f5dc819090d239c2f7e083de completed March 1, 2026, 9:50 p.m.
PD Predicate disambiguation batch_69a4b2aa219081908a6b0ef786b4aa52 completed March 1, 2026, 9:42 p.m.
Created at: March 1, 2026, 7:41 p.m.