Triple
T34988308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sub-Dean of Westminster |
E1009312
|
entity |
| Predicate | requiresPositionHolderToBe |
P88925
|
FINISHED |
| Object | ordained priest |
—
|
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: ordained priest | Statement: [Sub-Dean of Westminster, requiresPositionHolderToBe, ordained priest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresPositionHolderToBe Context triple: [Sub-Dean of Westminster, requiresPositionHolderToBe, ordained priest]
-
A.
requiredPositionHolder
Indicates that a specific entity is obligated to occupy or fulfill a particular position or role.
-
B.
positionHolderMust
chosen
Indicates that a person occupying a specific position is required or obligated to perform a certain action or fulfill a particular condition.
-
C.
requiresPriorPosition
Indicates that holding or completing a specified prior position, role, or status is a necessary prerequisite for the current position or action.
-
D.
holderMustBe
Indicates that a specified entity is required to be the holder or possessor of another entity or resource.
-
E.
previouslyIncludedPositionRequirement
Indicates that a position requirement existed or was included at an earlier time but is no longer part of the current set of requirements.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff8aff48988190a48a440de8238ef9 |
completed | May 9, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69ff8a780404819082f48ceb21e7fe11 |
completed | May 9, 2026, 7:26 p.m. |
Created at: May 3, 2026, 4:01 p.m.