Triple

T345328
Position Surface form Disambiguated ID Type / Status
Subject New York Court of Appeals E6927 entity
Predicate hasPositions P8266 FINISHED
Object Chief Judge of the New York Court of Appeals 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: Chief Judge of the New York Court of Appeals | Statement: [New York Court of Appeals, hasPositions, Chief Judge of the New York Court of Appeals]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPositions
Context triple: [New York Court of Appeals, hasPositions, Chief Judge of the New York Court of Appeals]
  • A. hasPositionOn chosen
    Indicates that one entity occupies or holds a specific role, job, or spatial location relative to another entity.
  • B. numberOfPositions
    Indicates the total count of distinct positions or roles associated with a given entity.
  • C. hasCoordinates
    Indicates that an entity is associated with specific spatial coordinates that define its position in a given reference system.
  • D. isPositionOf
    Indicates that one entity represents the spatial or organizational position or location of another entity.
  • E. appliesToPosition
    Indicates that something (such as a rule, condition, or attribute) is relevant or applicable to a specific position or role.
  • 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_69a2e7951ba08190960e90823b5078f3 completed Feb. 28, 2026, 1:03 p.m.
NER Named-entity recognition batch_69a2eb01261c81909280128b5ce75eff completed Feb. 28, 2026, 1:17 p.m.
PD Predicate disambiguation batch_69a2e95451a4819090f4e4fb9b21a493 completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.