Triple
T36757866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naustdal |
E908103
|
entity |
| Predicate | churchParish |
P2739
|
FINISHED |
| Object | Naustdal 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: Naustdal parish | Statement: [Naustdal, churchParish, Naustdal parish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: churchParish Context triple: [Naustdal, churchParish, Naustdal parish]
-
A.
parish
chosen
Indicates that an entity is administratively or ecclesiastically associated with a particular parish.
-
B.
isChristianParish
Indicates that one entity is a Christian parish, i.e., an administrative or ecclesiastical unit within a Christian church associated with a particular community or territory.
-
C.
parishIncludes
Indicates that a parish geographically or administratively contains or encompasses another entity or area.
-
D.
civilParishIn
Indicates that a civil parish is located within or administratively belongs to a specified larger geographic or governmental area.
-
E.
parishName
Indicates that an entity has the specified parish as its official or recorded name.
- F. None of above.
Provenance (3 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_69f76e779bec8190be0e1f87a131e0f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.