Triple
T32623584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anthony of Egypt |
E833993
|
entity |
| Predicate | tookVowOf |
P101277
|
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: [Anthony of Egypt, tookVowOf, poverty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookVowOf Context triple: [Anthony of Egypt, tookVowOf, poverty]
-
A.
tookReligiousVows
Indicates that an entity formally committed to a religious life by taking recognized vows within a religious tradition.
-
B.
tookReligiousVowsOn
Indicates that an entity formally committed to religious vows on a specific date or occasion.
-
C.
takesVowsOf
chosen
Indicates that an entity formally commits to specific vows, promises, or oaths, typically within a religious, ceremonial, or institutional context.
-
D.
vowedCelibacyWith
Indicates a mutual commitment between entities to abstain from sexual or romantic relationships, typically formalized as a shared vow of celibacy.
-
E.
tookSannyasaFrom
Indicates that one entity formally renounced worldly life and accepted the monastic or ascetic order under the guidance or authority of another 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:06 a.m.