Triple

T5147798
Position Surface form Disambiguated ID Type / Status
Subject Jesus of Suburbia E116115 entity
Predicate inUniverseSetting P47705 FINISHED
Object suburban America 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: suburban America | Statement: [Jesus of Suburbia, inUniverseSetting, suburban America]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inUniverseSetting
Context triple: [Jesus of Suburbia, inUniverseSetting, suburban America]
  • A. inUniverseType
    Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
  • B. inUniverse chosen
    Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
  • C. inUniverseRestriction
    Indicates that something is limited, applicable, or valid only within a specific fictional or defined universe or continuity.
  • D. inUniverseOrigin
    Indicates that one entity originates from, or has its source within, the fictional universe or setting defined by another entity.
  • E. inUniverseFunction
    Indicates that one entity serves a specific role, purpose, or function within the context or rules of a particular fictional or defined universe.
  • 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_69bd4446c0e08190a7c29dc74976bf03 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd78d7f4d081908d59adcd86f52f1d completed March 20, 2026, 4:42 p.m.
PD Predicate disambiguation batch_69bd77ae2f10819098bb8939106e1281 completed March 20, 2026, 4:37 p.m.
Created at: March 20, 2026, 1:43 p.m.