Triple

T9491437
Position Surface form Disambiguated ID Type / Status
Subject Johnson City Commission E228898 entity
Predicate hasExecutiveOversight P9597 FINISHED
Object yes 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: yes | Statement: [Johnson City Commission, hasExecutiveOversight, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasExecutiveOversight
Context triple: [Johnson City Commission, hasExecutiveOversight, yes]
  • A. hasSecurityOversightBy
    Indicates that the security responsibilities, controls, or governance for one entity are overseen, managed, or supervised by another entity.
  • B. oversightOfficial
    Indicates that one entity has formal responsibility for supervising, monitoring, or reviewing the actions or performance of another entity.
  • C. headOfGovernmentOversight chosen
    Indicates that one entity holds primary responsibility for supervising, directing, or managing the governmental activities or operations of another entity.
  • D. oversightFocus
    Indicates that one entity’s oversight, supervision, or monitoring activities are specifically directed toward another entity or aspect.
  • E. hasEnvironmentalOversightBy
    Indicates that one entity’s environmental practices, impacts, or compliance are monitored, regulated, or supervised by another 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_69ca847424f081908180305555139f7a completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd80c89ec48190a2ad49394cab9c56 completed April 1, 2026, 8:32 p.m.
PD Predicate disambiguation batch_69cca561e6b0819090aa795f3c3a2083 completed April 1, 2026, 4:56 a.m.
Created at: March 30, 2026, 7:56 p.m.