Triple

T485758
Position Surface form Disambiguated ID Type / Status
Subject Comptroller of New York E9871 entity
Predicate constitutionalOfficer P2259 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: [Comptroller of New York, constitutionalOfficer, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: constitutionalOfficer
Context triple: [Comptroller of New York, constitutionalOfficer, yes]
  • A. constitutionalPosition chosen
    Indicates the official role, office, or status an entity holds within a constitutional or legal framework.
  • B. isOfficerOf
    Indicates that one entity holds an official position, role, or office within another entity (such as an organization, group, or institution).
  • C. officeHolderOf
    Indicates that a person holds or has held an official position or role within a specified organization, institution, or office.
  • D. U.S.GovernmentPosition
    Indicates that an entity holds, held, or is associated with an official position or office within the United States government.
  • E. appointedByOffice
    Indicates that an entity attains its position or role through a formal appointment made by a specific office or official authority.
  • 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_69a2e802e2908190ab17c9479e0b6412 completed Feb. 28, 2026, 1:05 p.m.
NER Named-entity recognition batch_69a2f0bb46788190b40182bf2a54f98f completed Feb. 28, 2026, 1:42 p.m.
PD Predicate disambiguation batch_69a2edf48ec08190b85d07e194f99c49 completed Feb. 28, 2026, 1:30 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.