Triple

T13743623
Position Surface form Disambiguated ID Type / Status
Subject Larry Gold’s Studio E330155 entity
Predicate hasNotabilityScope P89495 FINISHED
Object regional 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: regional | Statement: [Larry Gold’s Studio, hasNotabilityScope, regional]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNotabilityScope
Context triple: [Larry Gold’s Studio, hasNotabilityScope, regional]
  • A. hasNotabilityCategory
    Indicates that an entity is associated with a particular category that characterizes its type or area of notability.
  • B. hasNotabilitySource
    Indicates that there exists an external, recognized source that attests to or supports the notability or significance of the subject entity.
  • C. hasNotabilityOrigin chosen
    Indicates that an entity’s notability or prominence arises from, or is primarily associated with, a specified origin (such as a place, context, or source).
  • D. hasNotabilityNote
    Indicates that there is an associated note or annotation explaining the significance, prominence, or special relevance of the subject.
  • E. lacksNotabilityAs
    Indicates that one entity is considered insufficiently notable or significant to be associated with or classified as the other entity.
  • 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_69d81c573f288190aa2403d484fa3d49 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de020855ec8190a60fa1cb761f2e68 completed April 14, 2026, 8:59 a.m.
PD Predicate disambiguation batch_69dbbe950b148190ba0df8a749269ec6 completed April 12, 2026, 3:47 p.m.
Created at: April 9, 2026, 10:07 p.m.