Triple

T14108437
Position Surface form Disambiguated ID Type / Status
Subject Dallas Division E339568 entity
Predicate hasVenueFor P112843 FINISHED
Object federal civil litigation arising in its counties 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: federal civil litigation arising in its counties | Statement: [Dallas Division, hasVenueFor, federal civil litigation arising in its counties]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasVenueFor
Context triple: [Dallas Division, hasVenueFor, federal civil litigation arising in its counties]
  • A. hasVenueIn
    Indicates that an event, activity, or occurrence takes place at a specific venue located within a particular geographic area or location.
  • B. hasVenueContext
    Indicates that an entity is associated with a particular venue or setting that provides contextual information about where it occurs or is situated.
  • C. hasVenueFunction
    Indicates that a venue serves a particular function or role (such as hosting events, performances, or specific activities).
  • D. hasPrincipalVenue
    Indicates that an entity has a primary or main venue where its activities, events, or operations predominantly take place.
  • E. hasHostedVenue
    Indicates that a particular venue has served as the location for hosting a specific event or activity.
  • 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_69d81c69b5c8819094aa1abf18302908 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de600caf308190ab6d8451ed4e3797 completed April 14, 2026, 3:41 p.m.
PD Predicate disambiguation batch_69de05b2f7e481908a9a7d40153234c0 completed April 14, 2026, 9:15 a.m.
PDg Predicate description generation batch_69de2398856c81908bed6070e4ca6ab1 completed April 14, 2026, 11:23 a.m.
Created at: April 9, 2026, 10:22 p.m.