Triple

T38627122
Position Surface form Disambiguated ID Type / Status
Subject West March E937343 entity
Predicate borderSystem P3948 FINISHED
Object Anglo-Scottish Marches 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: Anglo-Scottish Marches | Statement: [West March, borderSystem, Anglo-Scottish Marches]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: borderSystem
Context triple: [West March, borderSystem, Anglo-Scottish Marches]
  • A. borderIntegration
    Indicates the degree or manner in which two or more bordering regions are interconnected, coordinated, or functionally unified across their shared boundary.
  • B. borderRegime chosen
    Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
  • C. borderInternal
    Indicates that one entity lies within the interior of another and shares a common boundary with it, without touching the outer boundary of the containing entity.
  • D. borderServiceCategory
    Indicates a classification relationship where a border-related service is assigned to a specific service category or type.
  • E. borderConceptUsedBy
    Indicates that a conceptual boundary or limit is employed or referenced by another entity in its definition, use, or interpretation.
  • 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_69f76ed5ca3c81909288f61fbf37b359 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_6a0041860fd081908623ef9fd40a9775 completed May 10, 2026, 8:27 a.m.
PD Predicate disambiguation batch_6a00414b01488190a312adb3b25d69cf completed May 10, 2026, 8:26 a.m.
Created at: May 3, 2026, 4:32 p.m.