Triple
T34214246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pontifical university of the Catholic Church |
E877741
|
entity |
| Predicate | mayBeEntrustedTo |
P96404
|
FINISHED |
| Object | religious orders |
—
|
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: religious orders | Statement: [Pontifical university of the Catholic Church, mayBeEntrustedTo, religious orders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeEntrustedTo Context triple: [Pontifical university of the Catholic Church, mayBeEntrustedTo, religious orders]
-
A.
entrustedTo
chosen
Indicates that responsibility, care, or control of something has been formally given by one party to another.
-
B.
mayBeDelegatedTo
Indicates that a responsibility, task, or authority can be transferred from one entity to another to act on its behalf.
-
C.
mayHaveRole
Indicates that an entity is permitted or eligible to hold or perform a specified role.
-
D.
believedToGrant
Indicates that something is thought or assumed to provide, confer, or bestow a particular benefit, quality, or effect.
-
E.
mayGrant
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 1, 2026, 1:55 a.m.