Triple

T14579733
Position Surface form Disambiguated ID Type / Status
Subject Santiago E342155 entity
Predicate etymologicalOrigin P453 FINISHED
Object Santo Iago E1109221 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: Santo Iago | Statement: [Santiago, etymologicalOrigin, Santo Iago]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Santo Iago
Context triple: [Santiago, etymologicalOrigin, Santo Iago]
  • A. Santo Iago chosen
    Santo Iago is an older Spanish form of the name Santiago, traditionally associated with Saint James and the city that bears his name.
  • B. São Francisco de Paula
    São Francisco de Paula is a town in Brazil’s Rio Grande do Sul state, known for its cool climate, pine forests, and role as a scenic gateway to the Serra Gaúcha highlands.
  • C. Ciriaco
    Ciriaco is a variant of the name of Saint Cyriacus, an early Christian martyr venerated in various Christian traditions.
  • D. Obispo
    Obispo is a prominent summit of the El Altar volcanic complex in the Ecuadorian Andes, known for its rugged alpine terrain and challenging climbing routes.
  • E. Santo Tomás
    Santo Tomás is a town in the Cusco Region of Peru that serves as the administrative and commercial center of Chumbivilcas Province.
  • 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_69d822ddc0f081909cd8163c7de298cd completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb3f6f78c81908a30ecb4c025299d completed April 14, 2026, 9:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69fda91437e08190a41683f1777a8507 completed May 8, 2026, 9:12 a.m.
Created at: April 10, 2026, 1:24 a.m.