Triple

T2445057
Position Surface form Disambiguated ID Type / Status
Subject Duchy of Guelders E53371 entity
Predicate capital P234 FINISHED
Object Arnhem E12070 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: Arnhem | Statement: [Duchy of Guelders, capital, Arnhem]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Arnhem
Context triple: [Duchy of Guelders, capital, Arnhem]
  • A. Arnhem chosen
    Arnhem is a city in the eastern Netherlands best known as the site of a major World War II battle during Operation Market Garden.
  • B. Leeuwarden
    Leeuwarden is a historic city in the northern Netherlands, known as the capital of the province of Friesland and for its rich cultural and architectural heritage.
  • C. Papendrecht
    Papendrecht is a Dutch town situated on the river Merwede in the province of South Holland, known for its residential character and proximity to the city of Dordrecht.
  • D. Gorinchem
    Gorinchem is a historic fortified city in the Netherlands known for its well-preserved city walls and picturesque old town.
  • E. Roermond, Netherlands
    Roermond, Netherlands is a historic city in the southeastern province of Limburg known for its medieval architecture, riverside setting, and role as a regional commercial and cultural center.
  • 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_69ab495b6dac8190ac82661aa1452222 completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abca23ebe8819099a579a07c1bb708 completed March 7, 2026, 6:48 a.m.
NED1 Entity disambiguation (via context triple) batch_69aef0baa6448190a4046a039168b8fe completed March 9, 2026, 4:09 p.m.
Created at: March 6, 2026, 9:43 p.m.