Triple

T478948
Position Surface form Disambiguated ID Type / Status
Subject Inca Empire E9123 entity
Predicate capital P234 FINISHED
Object Cusco E21511 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: Cusco | Statement: [Inca Empire, capital, Cusco]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cusco
Context triple: [Inca Empire, capital, Cusco]
  • A. Cusco chosen
    Cusco is a historic city in southeastern Peru that served as the capital of the Inca Empire and is now a major gateway to Machu Picchu.
  • B. Arequipa
    Arequipa is Peru’s second-largest city, known for its colonial architecture built from white volcanic stone and its dramatic setting beneath the Misti volcano.
  • C. Sucre
    Sucre is the constitutional capital of Bolivia, known for its well-preserved colonial architecture and historical significance in the country’s independence.
  • D. Lima
    Lima is the capital and largest city of Peru, known as a major political, economic, and cultural center on South America's Pacific coast.
  • E. Trujillo
    Trujillo is a major coastal city in northwestern Peru known for its colonial architecture, cultural festivals, and proximity to important pre-Columbian archaeological sites.
  • 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_69a2e7ff81708190b0507a24a997232c completed Feb. 28, 2026, 1:05 p.m.
NER Named-entity recognition batch_69a2f056459881909749764cc4a7f9e8 completed Feb. 28, 2026, 1:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69a4711cd9ac8190bc95a6560950525b completed March 1, 2026, 5:02 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.