Triple

T4719808
Position Surface form Disambiguated ID Type / Status
Subject Yakutia E104734 entity
Predicate containsCity P294 FINISHED
Object Aldan E129692 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: Aldan | Statement: [Yakutia, containsCity, Aldan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aldan
Context triple: [Yakutia, containsCity, Aldan]
  • A. Aldan chosen
    Aldan is a mining town in Russia’s Sakha Republic known for its significant gold deposits and remote Siberian location.
  • B. Nadym
    Nadym is a town in the Yamalo-Nenets Autonomous Okrug of Russia, known as a regional center for the natural gas industry and served by its own airport.
  • C. Nain
    Nain is a remote coastal town in northern Labrador, Canada, known as the administrative center of the Inuit region of Nunatsiavut.
  • D. Namdrik
    Namdrik is a small inhabited atoll in the Marshall Islands known for its lagoon, traditional Marshallese culture, and copra production.
  • E. Novilara
    Novilara is an archaeological site and locality in the Marche region of Italy, known for its ancient Picene culture remains and notable funerary stelae.
  • 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_69bd43ec4a348190bc41afae43375e71 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6428e9e081908ce4041183cad13b completed March 20, 2026, 3:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69be39ff21f0819094a273a0f26b22f4 completed March 21, 2026, 6:26 a.m.
Created at: March 20, 2026, 1:18 p.m.