Triple
T7849469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Religious of the Sacred Heart of Mary |
E182006
|
entity |
| Predicate | vowsTaken |
P9696
|
FINISHED |
| Object | poverty |
—
|
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: poverty | Statement: [Religious of the Sacred Heart of Mary, vowsTaken, poverty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vowsTaken Context triple: [Religious of the Sacred Heart of Mary, vowsTaken, poverty]
-
A.
vowsTo
Indicates a commitment or solemn promise made by one entity to another to perform, uphold, or refrain from specific actions.
-
B.
primaryVows
chosen
Indicates that an entity has made or is bound by its main or foundational vows, promises, or commitments in a given context.
-
C.
oath
Indicates a formal, binding promise or pledge made by one party to uphold certain duties, truths, or obligations, often under conditions of solemnity or authority.
-
D.
hasOathTo
Indicates a relationship in which one entity is bound by an oath or sworn commitment to another entity.
-
E.
hasSpecialVowOfObedienceRegarding
Indicates that one entity is bound by a distinct or additional vow to obey the authority, directives, or will of another specific entity.
- 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_69ca82869ee08190b8f9040dbc2c0467 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb18e989ac819090e459b77d8932d3 |
completed | March 31, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cae92180f88190ae3d44c3de7adc93 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:50 p.m.