Triple

T16501776
Position Surface form Disambiguated ID Type / Status
Subject Neshnabémwen E400816 entity
Predicate alternateName P39 FINISHED
Object Neshnabemwin E400816 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: Neshnabemwin | Statement: [Neshnabémwen, alternateName, Neshnabemwin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Neshnabemwin
Context triple: [Neshnabémwen, alternateName, Neshnabemwin]
  • A. Neshnabémwen chosen
    Neshnabémwen is the Indigenous language of the Potawatomi people, belonging to the Algonquian language family and traditionally spoken in the Great Lakes region of North America.
  • B. Nawalane
    Nawalane is a residential neighborhood located within the Lyari area of Karachi, Pakistan.
  • C. Nasib
    Nasib is a given name most notably borne by Nasib Yusifbeyli, an Azerbaijani statesman and political figure of the early 20th century.
  • D. Mashíyyat
    Mashíyyat is the first month of the Badíʻ (Baháʼí) calendar, associated with the concept of the Divine Will.
  • E. Nabhanedishta
    Nabhanedishta is a lesser-known son of the Vedic lawgiver Shraddhadeva Manu mentioned in ancient Hindu scriptures.
  • 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_69d88381f6148190819958a038be990e completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e32e4f7b7c8190adb5a113f798484f completed April 18, 2026, 7:10 a.m.
NED1 Entity disambiguation (via context triple) batch_6a00582e6e288190825af8758097e325 completed May 10, 2026, 10:04 a.m.
Created at: April 10, 2026, 5:14 a.m.