Triple

T5543081
Position Surface form Disambiguated ID Type / Status
Subject Article 14: Boundaries E145338 entity
Predicate governsRelationshipWith P52773 FINISHED
Object neighboring U.S. states 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: neighboring U.S. states | Statement: [Article 14: Boundaries, governsRelationshipWith, neighboring U.S. states]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: governsRelationshipWith
Context triple: [Article 14: Boundaries, governsRelationshipWith, neighboring U.S. states]
  • A. governingPowerRelationship chosen
    Indicates a relationship where one entity holds authoritative control, influence, or ruling power over another entity.
  • B. definesRelationshipBetween
    Indicates that one entity specifies or establishes the nature, type, or rules of a relationship that exists between two or more other entities.
  • C. inRelationshipWith
    Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
  • D. governs
    Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
  • E. governedWith
    Indicates that two or more entities share or participate together in the act or process of governing.
  • 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_69c008fa64888190adae56c8f9ea4031 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c01fc947bc81908d1f7b709392ec20 completed March 22, 2026, 4:58 p.m.
PD Predicate disambiguation batch_69c01b0e72f08190bf705d8fe1639401 completed March 22, 2026, 4:38 p.m.
Created at: March 22, 2026, 3:35 p.m.