Triple

T34353945
Position Surface form Disambiguated ID Type / Status
Subject Øvre Romerike E881662 entity
Predicate hasNameInNorwegian P24009 FINISHED
Object Øvre Romerike
Øvre Romerike is a traditional district in Viken county in southeastern Norway, known for its agricultural landscape and proximity to Oslo and Oslo Airport, Gardermoen.
E2183392 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: Øvre Romerike | Statement: [Øvre Romerike, hasNameInNorwegian, Øvre Romerike]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Øvre Romerike
Triple: [Øvre Romerike, hasNameInNorwegian, Øvre Romerike]
Generated description
Øvre Romerike is a traditional district in Viken county in southeastern Norway, known for its agricultural landscape and proximity to Oslo and Oslo Airport, Gardermoen.

Provenance (5 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_69f349bd06008190904c2f86c42749e3 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f713f6aee08190903102d0e6633417 completed May 3, 2026, 9:23 a.m.
NED1 Entity disambiguation (via context triple) batch_6a39c3d7d4a88190aaf93d462477eb73 completed June 22, 2026, 11:23 p.m.
NEDg Description generation batch_6a39c5e5b10c8190bda0bfa7a37fc3b5 completed June 22, 2026, 11:31 p.m.
NED2 Entity disambiguation (via description) batch_6a39c699c0ac81909385b11d50af3927 completed June 22, 2026, 11:34 p.m.
Created at: May 1, 2026, 1:58 a.m.