Triple

T1368607
Position Surface form Disambiguated ID Type / Status
Subject Ingrian Finns E30058 entity
Predicate ethnonym P4709 FINISHED
Object Inkeriläiset E155937 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: Inkeriläiset | Statement: [Ingrian Finns, ethnonym, Inkeriläiset]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Inkeriläiset
Context triple: [Ingrian Finns, ethnonym, Inkeriläiset]
  • A. Inkeri chosen
    Inkeri refers to the Ingrian Finns, a Finnic ethnic group historically inhabiting the Ingria region near Saint Petersburg in northwestern Russia.
  • B. Sivaraksa
    Sivaraksa is the surname of Sulak Sivaraksa, a prominent Thai social activist, intellectual, and proponent of engaged Buddhism.
  • C. Leijonat
    Leijonat is the widely used Finnish nickname for Finland’s men’s national ice hockey team, literally meaning “The Lions.”
  • D. Lihir
    Lihir is an Oceanic language spoken primarily on the Lihir Islands of Papua New Guinea.
  • E. Vitasta
    Vitasta is the ancient Sanskrit name for the Jhelum River, a historically significant river of the Kashmir region frequently mentioned in Vedic and classical Indian texts.
  • 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_69a498f912008190a376a98b207b2071 completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c2d497f88190993d16a208ced43d completed March 1, 2026, 10:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69acd47f25c48190a27f87909c15d7c3 completed March 8, 2026, 1:44 a.m.
Created at: March 1, 2026, 7:57 p.m.