Triple
T153258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Society of Jesus |
E3476
|
entity |
| Predicate | additionalVow |
P7683
|
FINISHED |
| Object | special obedience to the Pope regarding missions |
—
|
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: special obedience to the Pope regarding missions | Statement: [Society of Jesus, additionalVow, special obedience to the Pope regarding missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: additionalVow Context triple: [Society of Jesus, additionalVow, special obedience to the Pope regarding missions]
-
A.
addedBells
Indicates that one entity has caused bells to be included or incorporated into another entity or context.
-
B.
addedTo
Indicates that one entity has been included or incorporated into another entity, typically as a new component, member, or element.
-
C.
vocalization
Indicates the act or manner of producing sounds or calls, typically as a means of communication.
-
D.
additionalMembersAllowed
Indicates that more members are permitted to be added beyond those already included or initially specified.
-
E.
canAlsoBe
Indicates that something has an additional possible state, role, or classification beyond its primary one.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a258e0b11c8190b7b5cf3c354c47ce |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a2565c727c8190bca9ba6ca52f216a |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a258de46888190835db2b21a093eaa |
completed | Feb. 28, 2026, 2:54 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.