Triple

T4037880
Position Surface form Disambiguated ID Type / Status
Subject Volga Federal District E83870 entity
Predicate hasImportantCity P316 FINISHED
Object Perm E129564 NE 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: Perm | Statement: [Volga Federal District, hasImportantCity, Perm]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Perm
Context triple: [Volga Federal District, hasImportantCity, Perm]
  • A. Perm chosen
    Perm is a major industrial and cultural city in the Ural region of Russia, situated on the Kama River and historically significant as a gateway between European and Asian Russia.
  • B. Per
    Per is a Scandinavian masculine given name, commonly used in Norway, Sweden, and Denmark as a form of Peter.
  • C. Perur
    Perur is a historic locality near Coimbatore in Tamil Nadu, India, known for its ancient temples and cultural significance.
  • D. Pal
    Pal is an Indian surname notably borne by Bipin Chandra Pal, a prominent nationalist leader in the Indian independence movement.
  • E. Pol
    Pol is a given name and variant of Paul, used in several European languages such as Catalan and French.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69aed92f7cf0819098e0539bdcc3767f completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefb3656f08190aa5286d951013646 completed March 9, 2026, 4:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5564436788190aff89ebfeeed6d9b completed March 14, 2026, 12:36 p.m.
Created at: March 9, 2026, 3:37 p.m.