Triple
T5402231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master of Sacred Theology |
E120803
|
entity |
| Predicate | mayPrepareFor |
P2534
|
FINISHED |
| Object | doctoral studies in theology |
—
|
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: doctoral studies in theology | Statement: [Master of Sacred Theology, mayPrepareFor, doctoral studies in theology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayPrepareFor Context triple: [Master of Sacred Theology, mayPrepareFor, doctoral studies in theology]
-
A.
preparesFor
chosen
Indicates that one entity is used, designed, or undertaken in order to get another entity ready for a future event, state, or activity.
-
B.
preparedFor
Indicates that one entity has been made ready, equipped, or arranged in anticipation of use by or in connection with another entity.
-
C.
preparationBy
Indicates that one entity is created, assembled, or made ready through the actions or processes performed by another entity.
-
D.
mayPresent
Indicates that one entity is permitted or authorized to present, display, or introduce another entity or item.
-
E.
mayEnter
Indicates that one entity is permitted or authorized to enter or access another entity or location.
- 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8932b8bc8190bd31e11b167a7212 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd84660ea08190a641084814fcf94d |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:04 p.m.