Triple
T66379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Trent |
E1323
|
entity |
| Predicate | affirmed |
P3106
|
FINISHED |
| Object | biblical canon of the Catholic Church |
—
|
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: biblical canon of the Catholic Church | Statement: [Council of Trent, affirmed, biblical canon of the Catholic Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affirmed Context triple: [Council of Trent, affirmed, biblical canon of the Catholic Church]
-
A.
affirms
chosen
Indicates that one entity explicitly confirms, supports, or asserts the truth or validity of another entity, statement, or proposition.
-
B.
approvedBy
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
C.
confirmedBy
Indicates that one entity validates, approves, or verifies the truth, accuracy, or occurrence of another entity or event.
-
D.
approves
Indicates that one entity formally accepts, authorizes, or agrees to a proposal, action, or decision made by another entity.
-
E.
concluded
Indicates that an entity has brought an event, process, discussion, or agreement to an end, often after reaching a decision or final judgment.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a2509b5a088190bb9d2b650aeb8bca |
completed | Feb. 28, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69a24ea749788190bc17865171ff909a |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.