Triple

T3411097
Position Surface form Disambiguated ID Type / Status
Subject Florida Orchestra E71894 entity
Predicate organizationScope P6976 FINISHED
Object regional orchestra 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 orchestra | Statement: [Florida Orchestra, organizationScope, regional orchestra]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: organizationScope
Context triple: [Florida Orchestra, organizationScope, regional orchestra]
  • A. organizationalScope chosen
    Indicates the range or extent of responsibility, authority, or applicability that an action, policy, or relationship has within an organization or its sub-units.
  • B. organizationContext
    Indicates that one entity operates within, is associated with, or is relevant to the organizational setting or environment defined by another entity.
  • C. identificationScope
    Indicates the contextual boundary or extent within which an entity is uniquely identified or recognized.
  • D. officeScope
    Indicates that a relationship, authority, or action is limited to, defined within, or applicable only in the context of a particular office or official position.
  • E. scopeType
    Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
  • 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_69ad85ac312481909e7027ced1456a9f completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb9094b2881909262e58a470ed9d0 completed March 8, 2026, 5:59 p.m.
PD Predicate disambiguation batch_69adadfcbc38819080852c18240451c5 completed March 8, 2026, 5:12 p.m.
Created at: March 8, 2026, 3:15 p.m.