Triple
T17657871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurum |
E440171
|
entity |
| Predicate | hasLandmark |
P105
|
FINISHED |
| Object | Hurum Church |
—
|
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: Hurum Church | Statement: [Hurum, hasLandmark, Hurum Church]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hurum Church Context triple: [Hurum, hasLandmark, Hurum Church]
-
A.
Hurum Church
chosen
Hurum Church is a historic parish church in Hurum, Norway, known for serving as a central religious and cultural landmark for the local community.
-
B.
Noresund Church
Noresund Church is a parish church serving the local community in the village of Noresund in Krødsherad, Norway.
-
C.
Udenes Church
Udenes Church is a historic parish church in Nes, Akershus, Norway, known for serving as a local center of Lutheran worship and community life.
-
D.
Finnås Church
Finnås Church is a historic parish church in Finnås, Norway, serving as a local center of Lutheran worship and community life.
-
E.
Valbo Church
Valbo Church is a historic parish church in Valbo, Sweden, serving as a central place of worship and community gathering for the local Lutheran congregation.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46ea3b4cc81908eec7032cf221d49 |
completed | April 19, 2026, 5:56 a.m. |
Created at: April 10, 2026, 9:28 a.m.