Triple

T6513005
Position Surface form Disambiguated ID Type / Status
Subject Arne E148181 entity
Predicate hasVariant P455 FINISHED
Object Arne (Norwegian form) E148181 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: Arne (Norwegian form) | Statement: [Arne, hasVariant, Arne (Norwegian form)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Arne (Norwegian form)
Context triple: [Arne, hasVariant, Arne (Norwegian form)]
  • A. Arne chosen
    Arne is a Scandinavian masculine given name commonly used in Norway, Sweden, and Denmark.
  • B. Arne
    Arne is a novella by Norwegian writer and Nobel laureate Bjørnstjerne Bjørnson, often regarded as a key work in 19th-century Norwegian literature for its portrayal of rural life and psychological depth.
  • C. Årnes
    Årnes is a small Norwegian town situated along the Glomma River, known as a local administrative and commercial center in Nes municipality in Viken county.
  • D. Ornes
    Ornes is a French village in the Meuse department that was completely destroyed during the Battle of Verdun in World War I and left as an uninhabited memorial site.
  • E. Erling
    Erling is a masculine given name of Scandinavian origin, commonly used in Norway and other Nordic countries.
  • 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_69c687e68e748190baceb9298f32d3ed completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c69f3db330819092503af4fb0649ea completed March 27, 2026, 3:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6cb69ca0c8190954dbe6c627981f3 completed March 27, 2026, 6:24 p.m.
Created at: March 27, 2026, 1:44 p.m.