Triple
T29725168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cinque Scole |
E752159
|
entity |
| Predicate | roofedMultipleCongregations |
P167641
|
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: [Cinque Scole, roofedMultipleCongregations, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roofedMultipleCongregations Context triple: [Cinque Scole, roofedMultipleCongregations, yes]
-
A.
inReligiousStructure
Indicates that one entity is located within or inside a building or structure used for religious purposes.
-
B.
isMajorReligiousBuildingOf
Indicates that a building serves as the primary or most significant religious structure associated with a particular religious group, institution, or area.
-
C.
religiousBuildingCount
Indicates the number of religious buildings associated with or present in a given context or entity.
-
D.
religiousBuildingTypePatronized
Indicates that an entity serves as a patron or supporter of a particular type of religious building.
-
E.
religiousBuildingInstanceOf
Indicates that a specific religious building is an instance of a particular class or type of religious building.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672ff16a08190b8840351bef56f55 |
completed | May 2, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 7:38 p.m.