Triple
T35686611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palestrina, Papal States |
E1031165
|
entity |
| Predicate | wasEcclesiasticalCenter |
P23109
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Palestrina, Papal States, wasEcclesiasticalCenter, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasEcclesiasticalCenter Context triple: [Palestrina, Papal States, wasEcclesiasticalCenter, yes]
-
A.
ecclesiasticalCenter
chosen
Indicates that a place functions as a primary religious or church administrative hub for a surrounding area or community.
-
B.
wasEcclesiasticalCentreUntilCentury
Indicates that a place functioned as an ecclesiastical (church or religious) center up to, but not beyond, a specified century.
-
C.
isEcclesiasticalBuilding
Indicates that a building is used primarily for religious or church-related purposes or functions.
-
D.
tookPlaceAtReligiousCenter
Indicates that an event or action occurred at a religious center or place of worship.
-
E.
isPrimatialChurchOf
Indicates that a church holds primatial status as the chief or leading church within a particular ecclesiastical jurisdiction or region.
- 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_69f76e0bb6608190ad3a1880be54a17d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.