Triple
T7606850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terry Jeffords |
E180127
|
entity |
| Predicate | isDevotedTo |
P77744
|
FINISHED |
| Object | family |
—
|
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: family | Statement: [Terry Jeffords, isDevotedTo, family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDevotedTo Context triple: [Terry Jeffords, isDevotedTo, family]
-
A.
associatedDevotion
Indicates a relationship where one entity is linked to or characterized by a particular devotion, dedication, or religious/spiritual practice connected to another entity.
-
B.
praysTo
Indicates that one entity directs a prayer, supplication, or act of worship toward another entity as its spiritual or divine recipient.
-
C.
veneratedBy
Indicates that one entity is regarded with deep respect, reverence, or worship by another entity.
-
D.
appliesToDeityIn
Indicates that something (such as a rule, attribute, or statement) is relevant or applicable to a deity within a specified context or domain.
-
E.
worshippedIn
Indicates that a particular deity, figure, or object of reverence is the focus of religious or spiritual worship within a specified place or context.
- F. None of above. chosen
Provenance (4 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_69c69f3567008190ab01d2ca7b53584a |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9fe10408190b1c12bb8f911cea8 |
completed | March 27, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e485f88190910b39da52a955fe |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8195e5c8190835e28d44e19f6ef |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:54 p.m.