Triple

T21775196
Position Surface form Disambiguated ID Type / Status
Subject Romerike E537552 entity
Predicate hasRegionalCenter P1474 FINISHED
Object Jessheim 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: Jessheim | Statement: [Romerike, hasRegionalCenter, Jessheim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jessheim
Context triple: [Romerike, hasRegionalCenter, Jessheim]
  • A. Jessheim chosen
    Jessheim is a town in Ullensaker, Norway, serving as a regional commercial and residential hub just northeast of Oslo.
  • B. Medeus
    Medeus is a character known as one of the children of Jason, sharing in the mythological legacy surrounding the hero’s family.
  • C. Medeus
    Medeus is a recurring dragon villain and final boss in the Fire Emblem video game series, known as the Earth Dragon who threatens the continent of Archanea.
  • D. Amon Amarth
    Amon Amarth is the fiery volcanic mountain in J.R.R. Tolkien’s Middle-earth where the One Ring is ultimately destroyed.
  • E. Hellum
    Hellum is a village in the Dutch province of Groningen, known for its historic church and rural character.
  • 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_69e0c470759c819094a215757113562b completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f04627bd488190bbc1fde8db417b55 completed April 28, 2026, 5:31 a.m.
Created at: April 16, 2026, 6:51 p.m.