Triple

T20679605
Position Surface form Disambiguated ID Type / Status
Subject Ingvar E508254 entity
Predicate etymologicalRoot P453 FINISHED
Object Proto-Germanic *Ingwaz NE NERFINISHED

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: Proto-Germanic *Ingwaz | Statement: [Ingvar, etymologicalRoot, Proto-Germanic *Ingwaz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Proto-Germanic *Ingwaz
Context triple: [Ingvar, etymologicalRoot, Proto-Germanic *Ingwaz]
  • A. Old English Tīw
    Old English Tīw is the name of the Germanic god of war and the sky, cognate with the Norse god Týr and reflected in the modern English weekday name Tuesday.
  • B. Proto-Germanic
    Proto-Germanic is the reconstructed common ancestor of all Germanic languages, including English, German, and the Norse languages.
  • C. Birgisch
    Birgisch is a small former municipality and village in the canton of Valais in southwestern Switzerland.
  • D. Ing (Germanic deity) chosen
    Ing is a Germanic deity, often associated with fertility and prosperity, whose name underlies various Germanic personal names and words.
  • E. Ripuarian
    Ripuarian is a group of closely related West Central German dialects spoken primarily in the Cologne region and surrounding areas along the Rhine.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4c1164881909a3bf1e3ddb2bc32 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6bea516b88190b3e90d03fa981a44 completed April 21, 2026, 12:02 a.m.
Created at: April 16, 2026, 11:44 a.m.