Triple
T5493343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commentary on Colossians |
E123752
|
entity |
| Predicate | placeInCanonCommented |
P62601
|
FINISHED |
| Object | Pauline epistles corpus |
—
|
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: Pauline epistles corpus | Statement: [Commentary on Colossians, placeInCanonCommented, Pauline epistles corpus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeInCanonCommented Context triple: [Commentary on Colossians, placeInCanonCommented, Pauline epistles corpus]
-
A.
hasPlaceInCanon
chosen
Indicates that something holds a specific status or position within an established canon or authoritative body of works.
-
B.
notInCanonOf
Indicates that something is excluded from, or does not belong to, the officially recognized canon of a given work or universe.
-
C.
hasPlaceInCanonLaw
Indicates that something holds a recognized status, role, or position within the system of canon law.
-
D.
followsInCanon
Indicates that one entity occurs later than and in continuity with another within an established narrative or canonical sequence.
-
E.
canonizedIn
Indicates that an authority formally declared someone to be a saint or holy figure in a specified place or institution.
- 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_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9281a0148190bb7a8dae9c991b9c |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a8df6481908d1643f7342fe6f0 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:10 p.m.