Triple
T13050678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GospelOfHebrews |
E327439
|
entity |
| Predicate | relationshipToCanonicalGospels |
P87381
|
FINISHED |
| Object | distinct from canonical Gospels |
—
|
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: distinct from canonical Gospels | Statement: [GospelOfHebrews, relationshipToCanonicalGospels, distinct from canonical Gospels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToCanonicalGospels Context triple: [GospelOfHebrews, relationshipToCanonicalGospels, distinct from canonical Gospels]
-
A.
numberOfCanonicalGospels
Indicates the count of canonical gospels associated with a given religious tradition or context.
-
B.
linkedToGospel
chosen
Indicates a relationship where something is connected or related to the gospel, typically in content, origin, or thematic focus.
-
C.
inChristianCanonOrder
Indicates that the entities are arranged according to the sequence used in the Christian biblical canon.
-
D.
positionAmongGospels
Indicates the numerical order or placement of a given gospel within the sequence of all gospels.
-
E.
sharesNewTestamentCanonWith
Indicates that two entities recognize and use the same set of New Testament canonical books.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98a9829b48190b23624b6b3df4600 |
completed | April 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69d9803aca4c8190b1015cd159cc47a9 |
completed | April 10, 2026, 10:56 p.m. |
Created at: April 9, 2026, 8:57 p.m.