Triple
T32939895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RSV Catholic Edition |
E842637
|
entity |
| Predicate | canonType |
P176376
|
FINISHED |
| Object | Catholic biblical canon |
—
|
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: Catholic biblical canon | Statement: [RSV Catholic Edition, canonType, Catholic biblical canon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonType Context triple: [RSV Catholic Edition, canonType, Catholic biblical canon]
-
A.
typeOfCanonry
Indicates that one canonry is classified as a specific kind or category of canonry in relation to another.
-
B.
givesCanon
Indicates that one entity provides or establishes an official or authoritative version (canon) of something for another entity or context.
-
C.
tipoDeCámara
Indicates the specific type or category of camera associated with an entity.
-
D.
usesCanon
Indicates that one entity employs or relies on another entity as its standard, reference, or authoritative source.
-
E.
inCanonWith
Indicates that two or more works, events, or elements are officially recognized as belonging to the same narrative continuity or canon.
- F. None of above. chosen
Provenance (4 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_69f34949727c81909d195c97de3341c8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6e029f0f88190b1f88d82a4a2cabd |
completed | May 3, 2026, 5:42 a.m. |
Created at: May 1, 2026, 1:20 a.m.