Triple

T11288675
Position Surface form Disambiguated ID Type / Status
Subject De Marne E267264 entity
Predicate hadSettlement P16159 FINISHED
Object Ulrum E759608 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: Ulrum | Statement: [De Marne, hadSettlement, Ulrum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ulrum
Context triple: [De Marne, hadSettlement, Ulrum]
  • A. Rigmor
    Rigmor is a feminine given name of Scandinavian origin, particularly used in Norway and Denmark.
  • B. Ulrych
    Ulrych is a variant spelling of the Germanic given name Ulrich, commonly used in Central and Eastern European contexts.
  • C. Ursem chosen
    Ursem is a village in the Dutch province of North Holland, known for its rural character and traditional polder landscape.
  • D. Hyllus
    Hyllus is a figure in Greek mythology known as the son of Heracles and Deianira, often associated with the Dorian invasion and the Heracleidae.
  • E. Urstein
    Urstein is a locality in the municipality of Puch bei Hallein in the Austrian state of Salzburg, known for hosting the Salzburg University of Applied Sciences campus.
  • 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_69d6aac993a08190a6f36445ebaf9a43 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e98875a08190b8509fe55e49d52d completed April 9, 2026, 6:01 p.m.
NED1 Entity disambiguation (via context triple) batch_69e4f48e190c8190b46d4286e2acaef1 completed April 19, 2026, 3:28 p.m.
Created at: April 8, 2026, 9:32 p.m.