Triple

T11810591
Position Surface form Disambiguated ID Type / Status
Subject Taensa E280860 entity
Predicate hasAlternativeName P39 FINISHED
Object Taensas E280860 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: Taensas | Statement: [Taensa, hasAlternativeName, Taensas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Taensas
Context triple: [Taensa, hasAlternativeName, Taensas]
  • A. Taensa chosen
    The Taensa are a Native American people historically associated with the lower Mississippi Valley region of what is now the southeastern United States.
  • B. Taan
    Taan is the Indigenous name for Prince of Wales Island, reflecting the traditional language and cultural heritage of its Native inhabitants.
  • C. Taasinge
    Taasinge is a Danish surname of likely Scandinavian origin, associated with individuals such as Carlotta Monterey.
  • D. Tiosa
    Tiosa is a town in the Amravati district of Maharashtra, India, known for its role as a local commercial and administrative center.
  • E. Taje
    Taje is an Austronesian language spoken in Central Sulawesi, Indonesia, belonging to the Tomini–Tolitoli subgroup.
  • 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_69d6ab26aae88190b2489efcb2a24234 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8a5ca50a081908a198b336d8c2b98 completed April 10, 2026, 7:24 a.m.
NED1 Entity disambiguation (via context triple) batch_69f13188b89c819095ba5d27de7ebbb2 completed April 28, 2026, 10:15 p.m.
Created at: April 8, 2026, 9:42 p.m.