Triple
T23185472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Diocese of Bielsko-Żywiec |
E579581
|
entity |
| Predicate | hasParishesInAndAround |
P96522
|
FINISHED |
| Object | Bielsko-Biała |
—
|
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: Bielsko-Biała | Statement: [Roman Catholic Diocese of Bielsko-Żywiec, hasParishesInAndAround, Bielsko-Biała]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParishesInAndAround Context triple: [Roman Catholic Diocese of Bielsko-Żywiec, hasParishesInAndAround, Bielsko-Biała]
-
A.
parishesIncluded
Indicates that certain parishes are contained within, or form part of, a larger administrative, geographic, or organizational unit.
-
B.
haveOwnParishes
chosen
Indicates that an entity possesses or is responsible for its own distinct parishes.
-
C.
hasCommunesNear
Indicates that one entity has communes located in its nearby geographic vicinity.
-
D.
numberOfParishes
Indicates the total count of parishes associated with a given entity.
-
E.
hasParishChurchesIn
Indicates that an entity possesses or is associated with one or more parish churches located within a specified area or jurisdiction.
- 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_69e245ff8000819090d12008805315b7 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f7230208190820acf52f537b3ff |
completed | April 29, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:05 p.m.