Triple

T38137096
Position Surface form Disambiguated ID Type / Status
Subject orphans' court division E952379 entity
Predicate mayBeServedBy P192621 FINISHED
Object judge of the court of common pleas 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: judge of the court of common pleas | Statement: [orphans' court division, mayBeServedBy, judge of the court of common pleas]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mayBeServedBy
Context triple: [orphans' court division, mayBeServedBy, judge of the court of common pleas]
  • A. mayServeAt
    Indicates that one entity is permitted or authorized to perform service or duties at a specified location, organization, or context.
  • B. isServedAt
    Indicates that something (such as food, drink, or a service) is provided or made available at a particular place or venue.
  • C. mayServe
    Indicates that one entity is permitted or authorized to provide a service or function to another entity.
  • D. mayProvideServiceIn
    Indicates that one entity is permitted or authorized to offer or perform a service within the scope, area, or context defined by another entity.
  • E. canBeServed
    Indicates that an entity is eligible or suitable to be provided, delivered, or made available for use or consumption.
  • 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_69f76f09a7148190a4b91c0bacdc127a completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fd19f791f48190bbb6f6047f9ddc59 completed May 7, 2026, 11:02 p.m.
PD Predicate disambiguation batch_69fd0df365948190bc9bfc7ffd46acd8 completed May 7, 2026, 10:10 p.m.
PDg Predicate description generation batch_69fd19f6a7888190aa7eee2b87687c53 completed May 7, 2026, 11:02 p.m.
Created at: May 3, 2026, 4:21 p.m.