Triple
T6186375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deloris Van Cartier |
E138069
|
entity |
| Predicate | roleAtConvent |
P37071
|
FINISHED |
| Object | choir director |
—
|
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: choir director | Statement: [Deloris Van Cartier, roleAtConvent, choir director]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtConvent Context triple: [Deloris Van Cartier, roleAtConvent, choir director]
-
A.
roleInMonasticism
chosen
Indicates the specific function, position, or status an entity holds within a monastic community or tradition.
-
B.
tookReligiousVows
Indicates that an entity formally committed to a religious life by taking recognized vows within a religious tradition.
-
C.
tookReligiousVowsOn
Indicates that an entity formally committed to religious vows on a specific date or occasion.
-
D.
sisterMonastery
Indicates a formal sister-monastery relationship between two monastic institutions, typically involving mutual support, affiliation, or shared spiritual ties.
-
E.
forcedIntoMonasticLifeBy
Indicates that one entity compelled another, against their will or under strong pressure, to enter and live a monastic or religious life.
- 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_69c008a8fd408190b7ec6e42934974a6 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0621671988190938dd16242a2e4d5 |
completed | March 22, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:19 p.m.