Triple
T19220406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grue municipality |
E480596
|
entity |
| Predicate | hasChurch |
P15000
|
FINISHED |
| Object | Grue 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: Grue Church | Statement: [Grue municipality, hasChurch, Grue Church]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Grue Church Context triple: [Grue municipality, hasChurch, Grue Church]
-
A.
Grue Church
chosen
Grue Church is a historic parish church located in the municipality of Grue in Innlandet county, Norway.
-
B.
Friezland Church
Friezland Church is a local place of Christian worship serving the community of Friezland in Greater Manchester, England.
-
C.
Ris Church
Ris Church is a Norwegian church in Oslo, best known as one of architect Arnstein Arneberg’s significant ecclesiastical designs.
-
D.
Ringebu Church
Ringebu Church is a historic Norwegian stave church in Innlandet county, renowned as one of the country’s largest and best-preserved medieval wooden churches.
-
E.
Vår Frue Church
Vår Frue Church is a historic medieval stone church and prominent landmark in central Trondheim, Norway.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa3e8d488190a93fb743dabd0ffb |
completed | April 20, 2026, 10:04 a.m. |
Created at: April 10, 2026, 1:24 p.m.