Triple

T34280710
Position Surface form Disambiguated ID Type / Status
Subject New York E879581 entity
Predicate wasPlaceOfJudicialServiceOf P11962 FINISHED
Object Samuel Nelson NE NERFINISHED

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: Samuel Nelson | Statement: [New York, wasPlaceOfJudicialServiceOf, Samuel Nelson]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasPlaceOfJudicialServiceOf
Context triple: [New York, wasPlaceOfJudicialServiceOf, Samuel Nelson]
  • A. heldJudicialPositionIn chosen
    Indicates that an entity served in an official judicial role or office within a specified jurisdiction or court.
  • B. workedAsJudgeOn
    Indicates that a person served in the role of a judge in connection with a particular case, court, or judicial proceeding.
  • C. hadJudicialFunction
    Indicates that an entity exercised or was assigned an official judicial role, authority, or responsibility in relation to another entity or context.
  • D. hasJudicialOfficer
    Indicates that an entity is associated with or served by a specific judicial officer (such as a judge or magistrate) responsible for legal or court-related functions.
  • E. servedAtCourtOf
    Indicates that an individual performed official duties or held a position in the court of a particular ruler or governing 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_69f349b5f6648190b9420d94a4cd16e0 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f71c35327c8190884f1bfe12bd2cd7 completed May 3, 2026, 9:58 a.m.
PD Predicate disambiguation batch_69f71822d0e88190ac9731c7ae5a4def completed May 3, 2026, 9:40 a.m.
Created at: May 1, 2026, 1:57 a.m.