Triple
T13661938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thérèse of Lisieux |
E327017
|
entity |
| Predicate | survivingSistersBecameNuns |
P68391
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Thérèse of Lisieux, survivingSistersBecameNuns, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivingSistersBecameNuns Context triple: [Thérèse of Lisieux, survivingSistersBecameNuns, 5]
-
A.
numberOfNuns
chosen
Indicates the quantity or count of nuns associated with a given entity.
-
B.
sisterMonastery
Indicates a formal sister-monastery relationship between two monastic institutions, typically involving mutual support, affiliation, or shared spiritual ties.
-
C.
forcedIntoMonasticLifeBy
Indicates that one entity compelled another, against their will or under strong pressure, to enter and live a monastic or religious life.
-
D.
sisterPillar
Indicates a relationship where one pillar is considered the sister (a closely related or counterpart structure) to another pillar.
-
E.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc620df208190afaccf3ddd10aa60 |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:52 p.m.