Triple
T916900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2 Maccabees |
E19791
|
entity |
| Predicate | apocryphalFor |
P19944
|
FINISHED |
| Object | most Protestant traditions |
—
|
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: most Protestant traditions | Statement: [2 Maccabees, apocryphalFor, most Protestant traditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apocryphalFor Context triple: [2 Maccabees, apocryphalFor, most Protestant traditions]
-
A.
textSourceApocrypha
chosen
Indicates that the referenced text originates from or is classified as apocryphal writings.
-
B.
notInCanonOf
Indicates that something is excluded from, or does not belong to, the officially recognized canon of a given work or universe.
-
C.
consideredHeresyBy
Indicates that a belief, practice, or doctrine is judged to be heretical by a particular authority, group, or tradition.
-
D.
liesBeyond
Indicates that one entity is located at a greater distance or outside the boundary of another reference point, region, or limit.
-
E.
inCanonOf
Indicates that one entity is officially recognized as part of the established canon or authoritative body of works associated with another entity.
- 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_69a4939f91a08190ba68c2c81eab90fe |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b6755c488190b7f7848110e3ea2c |
completed | March 1, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69a4b292d3408190947cbc2f794cf8c5 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:39 p.m.