Triple
T36436201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disputation XXIV |
E897589
|
entity |
| Predicate | hasAuthorReligiousOrder |
P144586
|
FINISHED |
| Object | Society of Jesus |
—
|
NE NERFINISHED |
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: Society of Jesus | Statement: [Disputation XXIV, hasAuthorReligiousOrder, Society of Jesus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorReligiousOrder Context triple: [Disputation XXIV, hasAuthorReligiousOrder, Society of Jesus]
-
A.
introducedByReligiousOrder
Indicates that something (such as a practice, institution, or idea) was initiated, established, or brought into use by a religious order.
-
B.
approvedReligiousOrder
Indicates that an authority has formally recognized and authorized a particular religious order.
-
C.
electeeReligiousOrder
chosen
Indicates that an electee is affiliated with, or a member of, a specific religious order.
-
D.
hasAuthorTheologicalAffiliation
Indicates that an author is associated with a particular theological tradition, denomination, or belief system.
-
E.
inspiredReligiousOrder
Indicates that one entity motivated, influenced, or served as a model for the founding or development of a particular religious order.
- 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_69f76e56636481908eda808ab0273401 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: May 3, 2026, 4:10 p.m.