Triple
T6655324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Friars Minor Conventual |
E150926
|
entity |
| Predicate | hasTypeOfVows |
P72121
|
FINISHED |
| Object | solemn 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: solemn vows | Statement: [Order of Friars Minor Conventual, hasTypeOfVows, solemn vows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfVows Context triple: [Order of Friars Minor Conventual, hasTypeOfVows, solemn vows]
-
A.
hasVow
Indicates that one entity has made or is bound by a formal vow or promise in relation to another entity or context.
-
B.
vowsTo
Indicates a commitment or solemn promise made by one entity to another to perform, uphold, or refrain from specific actions.
-
C.
hasTypeOfVoters
Indicates that an entity is associated with or characterized by a particular category or kind of voters.
-
D.
vowStatus
Indicates the current state or condition of a commitment or promise made between entities, such as whether it is active, fulfilled, or broken.
-
E.
hasDependentVowels
Indicates that a writing system or script uses vowel signs that are attached to or depend on consonant characters rather than standing alone as independent letters.
- F. None of above. chosen
Provenance (4 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_69c687f2c9508190a60b9aad31d3f358 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9d53848190ac75523c157249c6 |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad071b0081909b96dd4b93414bd1 |
completed | March 27, 2026, 4:15 p.m. |
| PDg | Predicate description generation | batch_69c6cc988c0081909d22b86ca299331c |
completed | March 27, 2026, 6:29 p.m. |
Created at: March 27, 2026, 2:01 p.m.