Triple

T16205618
Position Surface form Disambiguated ID Type / Status
Subject Alabama Probate Courts E393318 entity
Predicate hasVenueRule P118112 FINISHED
Object venue generally lies in county of decedent’s residence 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: venue generally lies in county of decedent’s residence | Statement: [Alabama Probate Courts, hasVenueRule, venue generally lies in county of decedent’s residence]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasVenueRule
Context triple: [Alabama Probate Courts, hasVenueRule, venue generally lies in county of decedent’s residence]
  • A. hasVenueRules chosen
    Indicates that specific rules or policies are associated with, or apply to, a particular venue.
  • B. hasPrincipalVenue
    Indicates that an entity has a primary or main venue where its activities, events, or operations predominantly take place.
  • C. hasQualifyingVenue
    Indicates that an entity is associated with a venue that meets specified qualifying criteria or standards.
  • D. hasVenueIn
    Indicates that an event, activity, or occurrence takes place at a specific venue located within a particular geographic area or location.
  • E. hasVenueContext
    Indicates that an entity is associated with a particular venue or setting that provides contextual information about where it occurs or is situated.
  • 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_69d87f1f5bd08190bd01cac0d5b9d2ef completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e2270f047c819084645da27759a3d2 completed April 17, 2026, 12:26 p.m.
PD Predicate disambiguation batch_69e219e11f6081909106b1240a17fd37 completed April 17, 2026, 11:30 a.m.
Created at: April 10, 2026, 5:03 a.m.