Triple
T18349245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Domenico Maggiore |
E439620
|
entity |
| Predicate | foundedAsConventFor |
P131461
|
FINISHED |
| Object | Dominican friars |
—
|
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: Dominican friars | Statement: [San Domenico Maggiore, foundedAsConventFor, Dominican friars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsConventFor Context triple: [San Domenico Maggiore, foundedAsConventFor, Dominican friars]
-
A.
placeOfMonasticFoundation
Indicates the location where a monastic community or monastery was originally established or founded.
-
B.
enteredConventAt
Indicates the point in time or age at which a person formally joined or was admitted into a convent.
-
C.
refoundedAsBenedictineMonastery
Indicates that something was re-established or reorganized specifically as a Benedictine monastery.
-
D.
sisterMonastery
Indicates a formal sister-monastery relationship between two monastic institutions, typically involving mutual support, affiliation, or shared spiritual ties.
-
E.
formerCistercianAbbey
Indicates that something was once a Cistercian abbey but no longer holds that status.
- 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e514f66a4c8190a0ba53d3b349178a |
completed | April 19, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e4561d665081908ec555344e76d82b |
completed | April 19, 2026, 4:12 a.m. |
Created at: April 10, 2026, 10:37 a.m.