Triple
T20018481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulstein |
E494783
|
entity |
| Predicate | hasLandmark |
P105
|
FINISHED |
| Object | Ulstein 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: Ulstein Church | Statement: [Ulstein, hasLandmark, Ulstein Church]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ulstein Church Context triple: [Ulstein, hasLandmark, Ulstein Church]
-
A.
Ulstein Church
chosen
Ulstein Church is a parish church of the Church of Norway located in the coastal town of Ulsteinvik in Møre og Romsdal county.
-
B.
Bleikvassli Church
Bleikvassli Church is a parish church of the Church of Norway located in the village of Bleikvasslia in Hemnes Municipality, Nordland county.
-
C.
Bremsnes Church
Bremsnes Church is a historic parish church located on the island of Averøya in Norway, serving as a local center of Lutheran worship and community life.
-
D.
Harestua Church
Harestua Church is a parish church serving the local community in the village of Harestua in Lunner, Norway.
-
E.
Eidfjord Church
Eidfjord Church is a parish church in Eidfjord, Norway, known for serving the local community as a place of Lutheran worship and cultural heritage.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6623e40748190b1abb0ead9acab4e |
completed | April 20, 2026, 5:28 p.m. |
Created at: April 11, 2026, 3:34 p.m.