Triple

T5422117
Position Surface form Disambiguated ID Type / Status
Subject Angolar Creole E121276 entity
Predicate alternativeName P39 FINISHED
Object Angolar E94969 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: Angolar | Statement: [Angolar Creole, alternativeName, Angolar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Angolar
Context triple: [Angolar Creole, alternativeName, Angolar]
  • A. Angolar chosen
    Angolar is a Portuguese-based creole language spoken primarily by the Angolar community on the island of São Tomé in São Tomé and Príncipe.
  • B. Anglona
    Anglona is a historical and geographical subregion in northern Sardinia, Italy, known for its rural landscapes, medieval villages, and traditional Sardinian culture.
  • C. Anga
    Anga was an ancient kingdom in the eastern Indian subcontinent, often noted in epic literature as the realm ruled by the warrior Karna.
  • D. Angi
    Angi is a digital marketplace that connects homeowners with local contractors and service professionals for home improvement and repair projects.
  • E. Agno
    Agno is a small Swiss town in the canton of Ticino, known for its lakeside location, regional airport, and proximity to Lugano.
  • 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_69bd463b58d88190b258261573de9e91 completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd87ec45c48190a8a25bf582b02440 completed March 20, 2026, 5:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf3ab7f6b481908fead172fbdafe36 completed March 22, 2026, 12:41 a.m.
Created at: March 20, 2026, 2:06 p.m.