Triple
T13050683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GospelOfHebrews |
E327439
|
entity |
| Predicate | containsTraditionAbout |
P29673
|
FINISHED |
| Object | baptism of Jesus |
—
|
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: baptism of Jesus | Statement: [GospelOfHebrews, containsTraditionAbout, baptism of Jesus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsTraditionAbout Context triple: [GospelOfHebrews, containsTraditionAbout, baptism of Jesus]
-
A.
mainTradition
Indicates that one entity represents the primary or dominant tradition associated with another entity.
-
B.
culturalTradition
Indicates a relationship where certain practices, beliefs, or customs are recognized as part of a shared cultural heritage passed down within a group or society.
-
C.
traditionAscribes
Indicates that a tradition attributes or assigns a particular quality, role, origin, or action to an entity.
-
D.
traditionIncludes
chosen
Indicates that a particular tradition encompasses, contains, or is composed of a specified element, practice, or component.
-
E.
linkedToTradition
Indicates a relationship where something is connected or related to a particular tradition, heritage, or customary practice.
- 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.