Triple
T8572621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Lolland-Falster |
E202963
|
entity |
| Predicate | parishesIncluded |
P83706
|
FINISHED |
| Object | parishes on the island of Lolland |
—
|
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: parishes on the island of Lolland | Statement: [Diocese of Lolland-Falster, parishesIncluded, parishes on the island of Lolland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parishesIncluded Context triple: [Diocese of Lolland-Falster, parishesIncluded, parishes on the island of Lolland]
-
A.
parishIncludes
Indicates that a parish geographically or administratively contains or encompasses another entity or area.
-
B.
numberOfParishes
Indicates the total count of parishes associated with a given entity.
-
C.
parishWith
Indicates that one entity is associated with, belongs to, or is administered together with another entity as part of the same parish.
-
D.
hasParishCommunity
Indicates that an entity is associated with, served by, or belongs to a specific parish community.
-
E.
parish
Indicates that an entity is administratively or ecclesiastically associated with a particular parish.
- F. None of above. chosen
Provenance (4 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_69ca8327b0a881908606ff860713964d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbea43843c8190ac2224d427bb7a75 |
completed | March 31, 2026, 3:37 p.m. |
| PD | Predicate disambiguation | batch_69cbd11856048190a1ce4b83a38f6965 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30e37ac8190b685df36274602b5 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:21 p.m.