Triple
T8930960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Peculiar |
E212651
|
entity |
| Predicate | authorityExemptFrom |
P36416
|
FINISHED |
| Object | diocesan bishop |
—
|
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: diocesan bishop | Statement: [Royal Peculiar, authorityExemptFrom, diocesan bishop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorityExemptFrom Context triple: [Royal Peculiar, authorityExemptFrom, diocesan bishop]
-
A.
exemptedFrom
chosen
Indicates that an entity is not subject to, or is formally released from, a rule, obligation, requirement, or liability that would otherwise apply.
-
B.
providesExemptionsTo
Indicates that one entity grants or offers exemptions, waivers, or exceptions from rules, obligations, or requirements to another entity.
-
C.
exemptionType
Indicates the specific category or kind of exemption that applies in a given context.
-
D.
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.
-
E.
deniedAuthorityOf
Indicates that one entity refused to recognize, accept, or submit to the authority, power, or legitimacy of 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_69ca8395c438819087d7cb844ab5990c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc668cdc0c8190b908fd23cbdef534 |
completed | April 1, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:57 p.m.