Triple
T1237684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic biblical canon |
E26582
|
entity |
| Predicate | dogmaticDefinitionYear |
P13858
|
FINISHED |
| Object | 1546 |
—
|
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: 1546 | Statement: [Roman Catholic biblical canon, dogmaticDefinitionYear, 1546]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dogmaticDefinitionYear Context triple: [Roman Catholic biblical canon, dogmaticDefinitionYear, 1546]
-
A.
dateOfDogmaticDefinition
chosen
Indicates the specific date on which a doctrine or teaching was formally and authoritatively defined as dogma.
-
B.
isDefinedAsDogmaBy
Indicates that one entity formally establishes or declares another entity as dogma or authoritative doctrine.
-
C.
yearOfPromulgation
Indicates the specific year in which something, typically a law or formal decree, was officially enacted or put into effect.
-
D.
defined
Indicates that one entity specifies, explains, or establishes the meaning, scope, or identity of another entity.
-
E.
claimedYear
Indicates the year that is asserted or reported as being associated with an event, status, or fact, regardless of whether it is verified.
- 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_69a4948571c88190a9191e451e6035fd |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf3f07c08190a402e8341c1f38cc |
completed | March 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69a4bb67d52c8190815d6356b79d6ed5 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.