Triple
T22312574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gjerdrum |
E551556
|
entity |
| Predicate | hasParish |
P35
|
FINISHED |
| Object | Gjerdrum parish |
—
|
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: Gjerdrum parish | Statement: [Gjerdrum, hasParish, Gjerdrum parish]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gjerdrum parish Context triple: [Gjerdrum, hasParish, Gjerdrum parish]
-
A.
Gjerdrum parish
chosen
Gjerdrum parish is a local Church of Norway parish serving the community of Gjerdrum in Viken county, Norway.
-
B.
Rygge parish
Rygge parish is a Church of Norway parish serving the local community in the Rygge area of Østfold, Norway.
-
C.
Fjell parish
Fjell parish is a Church of Norway parish serving the local community in the former Fjell municipality in western Norway.
-
D.
Kongsberg parish
Kongsberg parish is a Church of Norway parish centered in the town of Kongsberg, known for its historic mining heritage and prominent Kongsberg Church.
-
E.
Tjøtta parish
Tjøtta parish is a Church of Norway parish serving the Tjøtta area within the municipality of Alstahaug in Nordland county.
- 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1574f97cc81909685aeef15d02af9 |
completed | April 29, 2026, 12:56 a.m. |
Created at: April 16, 2026, 8:42 p.m.