Triple

T20506988
Position Surface form Disambiguated ID Type / Status
Subject Edwinton E503459 entity
Predicate territorialCapitalRelation P20536 FINISHED
Object predecessor name of city that became capital of North Dakota 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: predecessor name of city that became capital of North Dakota | Statement: [Edwinton, territorialCapitalRelation, predecessor name of city that became capital of North Dakota]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: territorialCapitalRelation
Context triple: [Edwinton, territorialCapitalRelation, predecessor name of city that became capital of North Dakota]
  • A. territorialCapital chosen
    Indicates that a location serves as the administrative or political capital of a defined territory or region.
  • B. governingTerritorialCapital
    Indicates that a territorial entity serves as the administrative or political capital for a governing body or jurisdiction.
  • C. territoryCapital
    Indicates that one entity is the capital city or administrative center of a specified territory.
  • D. regionCapital
    Indicates that one entity is the capital city or administrative center of a specified region.
  • E. countryCapitalRelation
    Indicates that one entity is the capital city of the country represented by the other 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_69e0b4b1e52c8190894281cf7e3283ab completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e69dc82dd0819085d64d65a1e72c70 completed April 20, 2026, 9:42 p.m.
PD Predicate disambiguation batch_69e59fcdf6e08190a604204615dc56e6 completed April 20, 2026, 3:38 a.m.
Created at: April 16, 2026, 11:36 a.m.