Triple

T30553228
Position Surface form Disambiguated ID Type / Status
Subject Maryland–Virginia maritime boundary E777621 entity
Predicate definesJurisdiction P6911 FINISHED
Object State of Maryland 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: State of Maryland | Statement: [Maryland–Virginia maritime boundary, definesJurisdiction, State of Maryland]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: definesJurisdiction
Context triple: [Maryland–Virginia maritime boundary, definesJurisdiction, State of Maryland]
  • A. definedJurisdictionOf chosen
    Indicates that one entity formally establishes or specifies the scope, boundaries, or authority of another entity’s jurisdiction.
  • B. usesJurisdiction
    Indicates that one entity applies or operates under the legal authority or rules of a particular jurisdiction.
  • C. legalDefinitionJurisdiction
    Indicates the jurisdiction or authority under which a particular legal definition is established or applies.
  • D. usesJurisdictionType
    Indicates that one entity applies, operates under, or is governed by a particular type or category of jurisdiction.
  • E. claimsJurisdictionOver
    Indicates that one authority or governing body asserts legal power or control over a particular area, matter, or 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_69f2249e19108190a458ab446096bf22 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fd5f29b1988190877764ef2a399c7f completed May 8, 2026, 3:57 a.m.
PD Predicate disambiguation batch_69fd5e30194c819085b5ce586122ab37 completed May 8, 2026, 3:53 a.m.
Created at: April 29, 2026, 8:20 p.m.