Triple
T36592811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O Clavis David |
E902714
|
entity |
| Predicate | titleUsedForChrist |
P179369
|
FINISHED |
| Object | Key of David |
—
|
NE NERFINISHED |
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: Key of David | Statement: [O Clavis David, titleUsedForChrist, Key of David]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleUsedForChrist Context triple: [O Clavis David, titleUsedForChrist, Key of David]
-
A.
hasChristologicalUse
Indicates that something is used or interpreted in a way that relates specifically to the person, nature, or work of Christ within Christian theology.
-
B.
titleUsedSince
Indicates that a particular title has been in use starting from a specified point in time.
-
C.
christologicalTitle
chosen
Indicates that one entity is identified as a Christological title (a theological designation related to Christ) of another entity.
-
D.
usedInChristianTradition
Indicates that something is employed, practiced, or recognized within Christian religious beliefs, rituals, or cultural traditions.
-
E.
ecclesiasticalTitleUsedIn
Indicates that a particular ecclesiastical (church) title is used within or applies to a specified context, such as a role, office, or jurisdiction.
- 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffbb1c5bf88190a0bf791213045885 |
completed | May 9, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69ffba0ab0f881908f84ef81f7a1bfe8 |
completed | May 9, 2026, 10:49 p.m. |
Created at: May 3, 2026, 4:11 p.m.