Triple

T1396768
Position Surface form Disambiguated ID Type / Status
Subject Toltec civilization E30683 entity
Predicate hasCapital P204 FINISHED
Object Tula E141975 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: Tula | Statement: [Toltec civilization, hasCapital, Tula]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tula
Context triple: [Toltec civilization, hasCapital, Tula]
  • A. Tula chosen
    Tula is an important ancient Mesoamerican city, once a major Toltec capital known for its monumental architecture and iconic stone warrior statues.
  • B. Tula
    Tula is a historic Russian city south of Moscow, known for its metalworking, samovar production, and as a cultural center near Leo Tolstoy’s estate at Yasnaya Polyana.
  • C. Solan
    Solan is a town in the Indian state of Himachal Pradesh known for its mushroom cultivation and as a growing commercial and educational hub in the region.
  • D. Ciudad Serdán
    Ciudad Serdán is a town in the Mexican state of Puebla, known as a gateway community to the nearby Pico de Orizaba volcano and surrounding highland region.
  • E. Tacuba
    Tacuba is a historic neighborhood in Mexico City known for its colonial-era architecture and role as a former pre-Hispanic town.
  • 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_69a498fd4e408190bd73eca30ea9754c completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c3817320819093067b1444d70b74 completed March 1, 2026, 10:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69ace56e32608190a03485d7cb5941a8 completed March 8, 2026, 2:56 a.m.
Created at: March 1, 2026, 7:59 p.m.