Triple

T1540588
Position Surface form Disambiguated ID Type / Status
Subject Pierce Butler E32855 entity
Predicate nominatedToCourtOn P30166 FINISHED
Object 1922-11-21 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: 1922-11-21 | Statement: [Pierce Butler, nominatedToCourtOn, 1922-11-21]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: nominatedToCourtOn
Context triple: [Pierce Butler, nominatedToCourtOn, 1922-11-21]
  • A. nominatedAsAssociateJusticeOn
    Indicates that an entity was formally selected or put forward to serve as an Associate Justice on a court or judicial body on a specific date or occasion.
  • B. nominatedAsChiefJusticeOn
    Indicates that an entity was formally selected or proposed to serve as Chief Justice on a specific date or occasion.
  • C. affectedCourt
    Indicates that a particular court is impacted or influenced by a specified action, decision, or legal matter.
  • D. courtOfficial
    Indicates that an entity serves in an official capacity within a court, holding an authorized role in judicial or legal proceedings.
  • E. associatedWithCourt
    Indicates a relationship in which an entity is linked or connected to a specific court, such as through jurisdiction, affiliation, or involvement in legal proceedings.
  • F. None of above. chosen

Provenance (4 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_69a885ed29088190a3c2d5a3d100c16e completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69aa95c1a2948190a2b98469afec1a7d completed March 6, 2026, 8:52 a.m.
PD Predicate disambiguation batch_69a907b2453c8190a41f6b88c8217d1e completed March 5, 2026, 4:33 a.m.
PDg Predicate description generation batch_69a93df847cc8190b6d011af33b34b40 completed March 5, 2026, 8:25 a.m.
Created at: March 4, 2026, 7:26 p.m.