Triple

T14800802
Position Surface form Disambiguated ID Type / Status
Subject Argobba E347903 entity
Predicate hasAlternativeName P39 FINISHED
Object Argoba E347903 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: Argoba | Statement: [Argobba, hasAlternativeName, Argoba]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Argoba
Context triple: [Argobba, hasAlternativeName, Argoba]
  • A. Urunga
    Urunga is a small coastal town in New South Wales, Australia, known for its scenic boardwalks, estuary views, and relaxed seaside atmosphere.
  • B. Garanhuns
    Garanhuns is a city in northeastern Brazil known for its mild climate, hilly terrain, and popular winter music festival.
  • C. Argobba chosen
    Argobba is an endangered South Semitic language spoken by the Argobba people in central Ethiopia.
  • D. Sabará
    Sabará is a historic colonial-era city in southeastern Brazil known for its well-preserved baroque architecture and gold-mining heritage.
  • E. Opata
    Opata refers to an Indigenous people and their now largely extinct Uto-Aztecan language historically spoken in northern Mexico, particularly in the present-day state of Sonora.
  • 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_69d822ea8b7c819097dfadf3d45545e6 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69decd62c36c81909c2993dc7d1a79ea completed April 14, 2026, 11:27 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe24c4f690819087504fcfd2df8ba3 completed May 8, 2026, 6 p.m.
Created at: April 10, 2026, 1:31 a.m.