Triple
T35225490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varteig |
E1017081
|
entity |
| Predicate | historicalParishOf |
P101108
|
FINISHED |
| Object | Church of Norway |
—
|
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: Church of Norway | Statement: [Varteig, historicalParishOf, Church of Norway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalParishOf Context triple: [Varteig, historicalParishOf, Church of Norway]
-
A.
isHistoricParishOf
chosen
Indicates that one entity is a historic parish that formerly served, or is recognized as having served, as the parish jurisdiction for another entity.
-
B.
hasParishHistory
Indicates that an entity possesses or is associated with a documented historical record of a parish.
-
C.
hasHistoricParishCharacter
Indicates that something possesses the distinctive qualities or attributes traditionally associated with a historic parish.
-
D.
historicalTownshipOf
Indicates that one entity was formerly a township encompassing or governing the other entity during a past historical period.
-
E.
governingDioceseHistorical
Indicates that one diocese historically exercised governing authority or jurisdiction over another ecclesiastical entity.
- 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_69f76de072908190ab65038a8a7b6a79 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00a846a8f881908b073ad13a5af6ca |
completed | May 10, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_6a00a7aae194819085e1a2fd406f7922 |
completed | May 10, 2026, 3:43 p.m. |
Created at: May 3, 2026, 4:02 p.m.