Triple

T22740243
Position Surface form Disambiguated ID Type / Status
Subject Shinkyō E562390 entity
Predicate establishedAsCapitalBy P5604 FINISHED
Object Japanese authorities in Manchukuo 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: Japanese authorities in Manchukuo | Statement: [Shinkyō, establishedAsCapitalBy, Japanese authorities in Manchukuo]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: establishedAsCapitalBy
Context triple: [Shinkyō, establishedAsCapitalBy, Japanese authorities in Manchukuo]
  • A. inauguratedAsCapital chosen
    Indicates that a place was officially declared and established as the capital of a political or administrative entity.
  • B. succeededAsCapitalBy
    Indicates that one capital city has been replaced by another as the official capital of a political entity.
  • C. servedAsNationalCapitalFrom
    Indicates that a place functioned as the national capital of a country or political entity during a specified time period.
  • D. wasDeFactoCapitalOf
    Indicates that a place functioned in practice as the capital of a political entity, even if it was not officially designated as such.
  • E. wasPrecededAsCapitalBy
    Indicates that one entity served as a capital city immediately before another entity became the capital.
  • 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_69e245513a5c81908d5cb471b4fc429d completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f1797241588190be67db7a37a88f23 completed April 29, 2026, 3:22 a.m.
PD Predicate disambiguation batch_69eed2a971c0819088af574e40c9343f completed April 27, 2026, 3:06 a.m.
Created at: April 17, 2026, 3:23 p.m.