Triple
T4578324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catholic religious orders |
E101792
|
entity |
| Predicate | mayIncludeVow |
P53912
|
FINISHED |
| Object | vow of stability |
—
|
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: vow of stability | Statement: [Catholic religious orders, mayIncludeVow, vow of stability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayIncludeVow Context triple: [Catholic religious orders, mayIncludeVow, vow of stability]
-
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.
mayIncludeFeature
chosen
Indicates that one entity is allowed or able to contain, incorporate, or be associated with a particular feature.
-
C.
additionalVow
Indicates that an entity makes or is associated with an extra or supplementary vow beyond an initial or primary vow.
-
D.
maySpeak
Indicates that one entity is permitted or allowed to speak to, or communicate verbally with, another entity.
-
E.
mayNot
Indicates that an entity is not permitted or is prohibited from performing a particular action or entering into a specified relationship.
- 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_69bd43d4ce208190b53158c882b222e3 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd58e2a1808190be4582d5b3003d6c |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5228b70c8190ac48705e35a710c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.