Triple
T23463041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Certosa di Trisulti |
E569032
|
entity |
| Predicate | convertedToCarthusianMonasteryIn |
P152368
|
FINISHED |
| Object | 13th century |
—
|
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: 13th century | Statement: [Certosa di Trisulti, convertedToCarthusianMonasteryIn, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convertedToCarthusianMonasteryIn Context triple: [Certosa di Trisulti, convertedToCarthusianMonasteryIn, 13th century]
-
A.
convertedToCistercian
Indicates that an entity has changed its religious affiliation or institutional status to become part of the Cistercian order.
-
B.
enteredConvent
Indicates that a person has joined and been admitted into a religious convent as a member.
-
C.
enteredConventAt
Indicates the point in time or age at which a person formally joined or was admitted into a convent.
-
D.
forcedIntoMonasticLifeBy
Indicates that one entity compelled another, against their will or under strong pressure, to enter and live a monastic or religious life.
-
E.
wasMonkOf
Indicates that a person was a member or monk belonging to a particular religious order, monastery, or monastic community.
- 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a69cf7c48190b4d44e500f955b99 |
completed | April 29, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:54 p.m.