Triple

T27555325
Position Surface form Disambiguated ID Type / Status
Subject Mitchell v. Helms E695619 entity
Predicate hasLocationOfDispute P69048 FINISHED
Object Jefferson Parish, Louisiana 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: Jefferson Parish, Louisiana | Statement: [Mitchell v. Helms, hasLocationOfDispute, Jefferson Parish, Louisiana]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLocationOfDispute
Context triple: [Mitchell v. Helms, hasLocationOfDispute, Jefferson Parish, Louisiana]
  • A. defendantLocation
    Indicates the place or jurisdiction where the defendant is located or resides in relation to a legal matter.
  • B. jurisdictionOfTribunal
    Indicates the legal authority or scope within which a particular tribunal is empowered to hear and decide cases.
  • C. locationOfLawChallenged chosen
    Indicates the jurisdiction or place in which a particular law is being contested or legally challenged.
  • D. disputedLocation
    Indicates that the geographic location is claimed or controlled by multiple parties, with no universally recognized agreement on its status or ownership.
  • E. disputeInvolves
    Indicates that a particular dispute includes or concerns the specified entities as participants or parties to the conflict.
  • 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_69ef5387e97c8190a9dab040d21cd048 completed April 27, 2026, 12:16 p.m.
NER Named-entity recognition batch_69f73ae120bc8190bff94d38d7a7a00d completed May 3, 2026, 12:09 p.m.
PD Predicate disambiguation batch_69f73a38d0848190aa5139144b8561c6 completed May 3, 2026, 12:06 p.m.
Created at: April 27, 2026, 1:36 p.m.