Triple

T4592296
Position Surface form Disambiguated ID Type / Status
Subject Arnhemmer E103520 entity
Predicate hasAlternativeForm P455 FINISHED
Object Arnhemse (f) E103520 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: Arnhemse (f) | Statement: [Arnhemmer, hasAlternativeForm, Arnhemse (f)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Arnhemse (f)
Context triple: [Arnhemmer, hasAlternativeForm, Arnhemse (f)]
  • A. Arnhemmer chosen
    An Arnhemmer is a resident or native of the Dutch city of Arnhem in the province of Gelderland.
  • B. ’s-Heer Arendskerke
    ’s-Heer Arendskerke is a small village in the Dutch province of Zeeland, known for its rural character and historic church.
  • C. Goudswaard
    Goudswaard is a small village in the Dutch province of South Holland, known for its rural character and location on the island of Hoeksche Waard.
  • D. Grembergen
    Grembergen is a village in East Flanders, Belgium, known as the birthplace of the Symbolist painter Fernand Khnopff.
  • E. Heusden
    Heusden is a historic fortified town in the southern Netherlands known for its well-preserved ramparts and picturesque old harbor.
  • 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_69bd43dccaf08190aa89e9991a289719 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd592520ec8190b1bd4cb4d9b94c94 completed March 20, 2026, 2:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69bde0d553f08190a56020e1bf8f700d completed March 21, 2026, 12:05 a.m.
Created at: March 20, 2026, 1:11 p.m.