Triple
T19579933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skien Church |
E489958
|
entity |
| Predicate | hasParishPopulationServed |
P79065
|
FINISHED |
| Object | local community of Skien |
—
|
LITERAL FINISHED |
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: local community of Skien | Statement: [Skien Church, hasParishPopulationServed, local community of Skien]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParishPopulationServed Context triple: [Skien Church, hasParishPopulationServed, local community of Skien]
-
A.
hasServiceAreaPopulation
Indicates that an entity has a service area characterized by a specific population size or count.
-
B.
hasParishFunction
Indicates that an entity performs, fulfills, or is assigned a specific functional role within a parish.
-
C.
servesPopulationCentre
chosen
Indicates that one entity provides services or functions in support of a particular population centre.
-
D.
hasParishCommunity
Indicates that an entity is associated with, served by, or belongs to a specific parish community.
-
E.
hasParishionersFrom
Indicates that a religious institution or parish includes parishioners who come from a specified place or group.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6402763b8819099e535979f094f9d |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:42 p.m.