Triple

T1484527
Position Surface form Disambiguated ID Type / Status
Subject Maryland–West Virginia boundary (traditional) E29434 entity
Predicate hasDisputes P23974 FINISHED
Object boundary interpretation between Maryland and Virginia 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: boundary interpretation between Maryland and Virginia | Statement: [Maryland–West Virginia boundary (traditional), hasDisputes, boundary interpretation between Maryland and Virginia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDisputes
Context triple: [Maryland–West Virginia boundary (traditional), hasDisputes, boundary interpretation between Maryland and Virginia]
  • A. hasDisputeHistory
    Indicates that there has been at least one prior dispute or conflict involving the related entities.
  • B. hasDisputedStatus chosen
    Indicates that the status or classification of something is contested, uncertain, or not universally agreed upon.
  • C. handlesDisputesOver
    Indicates that one entity is responsible for managing, resolving, or adjudicating disputes concerning another entity.
  • D. statusDisputedBy
    Indicates that the validity, accuracy, or recognition of a status is being challenged or contested by a specified party.
  • E. hasDisputedIdentityWith
    Indicates that two entities are associated with conflicting, uncertain, or contested identifications, such that their true or correct identities are in dispute relative to each other.
  • 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_69a498da82e08190ba833330d05f380f completed March 1, 2026, 7:51 p.m.
NER Named-entity recognition batch_69a4c6a011f0819086e9ee517ed6d29f completed March 1, 2026, 11:07 p.m.
PD Predicate disambiguation batch_69a4c486eacc81909c272f9bdf50a7c3 completed March 1, 2026, 10:58 p.m.
Created at: March 1, 2026, 8:12 p.m.