Triple
T6500750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Fathers |
E148878
|
entity |
| Predicate | typeOfVows |
P9696
|
FINISHED |
| Object | religious vows |
—
|
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: religious vows | Statement: [White Fathers, typeOfVows, religious vows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfVows Context triple: [White Fathers, typeOfVows, religious vows]
-
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.
vowStatus
Indicates the current state or condition of a commitment or promise made between entities, such as whether it is active, fulfilled, or broken.
-
D.
vowedVirtue
Indicates that an entity has formally promised or committed to uphold a particular virtue or moral quality.
-
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_69c687e9ad288190bae5bcac9c8ac855 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f386aa08190bfc8592a92ec6339 |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab714908190aa7c2fbf64078e15 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:42 p.m.