Triple
T2379466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epistle of Jude |
E46275
|
entity |
| Predicate | containsReferenceTo |
P8581
|
FINISHED |
| Object | Old Testament examples of judgment |
—
|
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: Old Testament examples of judgment | Statement: [Epistle of Jude, containsReferenceTo, Old Testament examples of judgment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsReferenceTo Context triple: [Epistle of Jude, containsReferenceTo, Old Testament examples of judgment]
-
A.
isReferencedIn
chosen
Indicates that one entity is cited, mentioned, or otherwise referred to within another entity.
-
B.
isReferencePointFor
Indicates that one entity serves as a positional or conceptual basis used to locate, measure, or interpret another entity.
-
C.
hasNotableReference
Indicates that one entity makes a significant or noteworthy mention of, or allusion to, another entity.
-
D.
hasReferencePolicy
Indicates that an entity is governed by or associated with a specific reference policy that defines how it should be used, accessed, or managed.
-
E.
hasMainReferent
Indicates that one entity serves as the primary or central referent for another entity within a given context.
- 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_69a88a1554a48190a0180682bcf099be |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc7b60c8c819080e4f682e4362a93 |
completed | March 7, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69abc59f73f08190924a36d7d475d8f4 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.