Triple
T20277715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Servolo |
E503058
|
entity |
| Predicate | hasReligiousPast |
P111
|
FINISHED |
| Object | Catholic monastic community |
—
|
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: Catholic monastic community | Statement: [San Servolo, hasReligiousPast, Catholic monastic community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousPast Context triple: [San Servolo, hasReligiousPast, Catholic monastic community]
-
A.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
B.
hasFormerReligiousJurisdiction
Indicates that an entity was previously under the religious authority or governance of another entity, but no longer is.
-
C.
formerReligiousAffiliation
chosen
Indicates that an entity previously adhered to a particular religion or religious denomination but no longer does so.
-
D.
hasAssociatedReligion
Indicates that an entity is connected with or linked to a particular religion.
-
E.
hasDenominationalBackground
Indicates that an entity is associated with or originates from a particular religious denomination or tradition.
- 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_69e0b4b0e79c8190bd61f22ef1329fa8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e675e4cdfc81908c7cb4519a7d744b |
completed | April 20, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 10:35 a.m.