Triple

T34586141
Position Surface form Disambiguated ID Type / Status
Subject Judge Taylor E888048 entity
Predicate appointsCounsel P3344 FINISHED
Object Atticus Finch 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: Atticus Finch | Statement: [Judge Taylor, appointsCounsel, Atticus Finch]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: appointsCounsel
Context triple: [Judge Taylor, appointsCounsel, Atticus Finch]
  • A. appointedWith
    Indicates that one entity has been formally assigned or designated to a role, position, or responsibility in relation to another entity.
  • B. appointedIn
    Indicates that an entity is formally assigned or designated to a role, position, or office within a specific context, organization, or jurisdiction.
  • C. appointedAs
    Indicates that one entity is formally assigned or designated to hold a specific role, position, or title in relation to another entity.
  • D. appointedFor chosen
    Indicates that an entity has been officially assigned or designated to perform a specific role, task, or function for another entity or purpose.
  • E. appointedWithin
    Indicates that one entity was formally appointed to a role, position, or office inside the organizational, temporal, or structural bounds defined 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_69f349d25cbc8190869998de5915886b completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69fd44474ed48190ac372e4c88d762ed completed May 8, 2026, 2:02 a.m.
PD Predicate disambiguation batch_69fd41ef28a48190a66959be5c964461 completed May 8, 2026, 1:52 a.m.
Created at: May 1, 2026, 2:03 a.m.