Triple
T12668227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mother Superior (Sister Act) |
E302611
|
entity |
| Predicate | authorityRole |
P106191
|
FINISHED |
| Object | religious superior |
—
|
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 superior | Statement: [Mother Superior (Sister Act), authorityRole, religious superior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorityRole Context triple: [Mother Superior (Sister Act), authorityRole, religious superior]
-
A.
ownerRole
Indicates the role or capacity in which an entity serves as the owner of another entity.
-
B.
antRole
Indicates that one entity has a specific role, function, or responsibility in relation to another entity.
-
C.
authorityGranted
Indicates that one entity has formally given another entity the power, rights, or permission to act or make decisions, typically within a defined scope or context.
-
D.
ordinationRole
Indicates the specific religious or ceremonial office, function, or capacity in which an entity is formally ordained.
-
E.
libraryRole
Indicates the specific function, responsibility, or position an entity holds within the context of a library.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d961acadb8819098de743bc951fedb |
completed | April 10, 2026, 8:46 p.m. |
Created at: April 9, 2026, 5:20 p.m.