Triple
T4557740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Test Act 1673 |
E120519
|
entity |
| Predicate | doctrineDenied |
P5486
|
FINISHED |
| Object | transubstantiation |
—
|
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: transubstantiation | Statement: [Test Act 1673, doctrineDenied, transubstantiation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doctrineDenied Context triple: [Test Act 1673, doctrineDenied, transubstantiation]
-
A.
deniedAuthorityOf
Indicates that one entity refused to recognize, accept, or submit to the authority, power, or legitimacy of another entity.
-
B.
deniesDoctrine
chosen
Indicates that one entity rejects, opposes, or refuses to accept the truth or validity of a particular doctrine associated with another entity.
-
C.
cannotGrant
Indicates that an entity lacks the authority, permission, or ability to confer a requested right, access, or resource to another entity.
-
D.
typicallyDenies
Indicates that an entity, in most usual or common circumstances, refuses, rejects, or does not grant something to another entity.
-
E.
notAuthorizedFor
Indicates that an entity lacks the required permission or authority to perform a specific action or access a particular resource.
- 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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd58163e6081909d5a3aae12c42a00 |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.