Triple

T34637448
Position Surface form Disambiguated ID Type / Status
Subject Tennessee and Virginia E889466 entity
Predicate shareBorderDisputesHistorical P93966 FINISHED
Object historical surveying and boundary disputes in 18th–19th centuries 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: historical surveying and boundary disputes in 18th–19th centuries | Statement: [Tennessee and Virginia, shareBorderDisputesHistorical, historical surveying and boundary disputes in 18th–19th centuries]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: shareBorderDisputesHistorical
Context triple: [Tennessee and Virginia, shareBorderDisputesHistorical, historical surveying and boundary disputes in 18th–19th centuries]
  • A. borderHistory
    Indicates the historical changes, events, or status of borders between entities over time.
  • B. hasSharedBorderHistoryWith chosen
    Indicates that two entities have a history of sharing a common border or boundary at some point in time.
  • C. borderDisputeResolvedBy
    Indicates that a previously contested border between entities has been settled or resolved through the specified agent, process, or agreement.
  • D. historicBoundaryFor
    Indicates that one entity serves as a historical boundary or border associated with another entity, typically reflecting past territorial or administrative limits.
  • E. shareBorderAgreement
    Indicates that two entities have a formally recognized agreement concerning their shared border.
  • 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_69f349d724848190b63ad3407e0006d9 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_6a0027e4a59481909417b2531daaf480 completed May 10, 2026, 6:38 a.m.
PD Predicate disambiguation batch_6a0026a42bc08190ad3322ce625a523a completed May 10, 2026, 6:33 a.m.
Created at: May 1, 2026, 2:04 a.m.