Triple
T4944258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglican authorities |
E111007
|
entity |
| Predicate | deriveAuthorityFrom |
P18538
|
FINISHED |
| Object | English law |
—
|
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: English law | Statement: [Anglican authorities, deriveAuthorityFrom, English law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deriveAuthorityFrom Context triple: [Anglican authorities, deriveAuthorityFrom, English law]
-
A.
definesAuthority
Indicates that one entity has the formal power or right to make decisions, control, or govern another entity or domain.
-
B.
usesAuthorityOf
chosen
Indicates that one entity exercises power, rights, or influence derived from or on behalf of another entity’s authority.
-
C.
authoritativeFor
Indicates that one entity has recognized control, responsibility, or decision-making power over another entity or domain.
-
D.
bindingAuthorityFor
Indicates that one entity has the legal or formal power to create obligations or make decisions that are binding on another entity.
-
E.
addressesAuthority
Indicates that one entity directs communication, requests, or appeals to another entity recognized as having authority or decision-making power.
- 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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd70a8e5388190882831d7828441d3 |
completed | March 20, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3aa1388190b3e0c8ee1ba1e4fa |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:31 p.m.