Triple
T23747004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armor of God (Bible study) |
E586843
|
entity |
| Predicate | focusPassage |
P153543
|
FINISHED |
| Object | Ephesians 6:10–18 |
—
|
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: Ephesians 6:10–18 | Statement: [Armor of God (Bible study), focusPassage, Ephesians 6:10–18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusPassage Context triple: [Armor of God (Bible study), focusPassage, Ephesians 6:10–18]
-
A.
focusIssue
Indicates that an issue, topic, or problem is the primary subject of attention or concern in a given context.
-
B.
focusType
Indicates the specific kind or category of focus or attention that is being applied to or associated with an entity or interaction.
-
C.
focusTheory
Indicates that one entity serves as the primary theoretical framework, perspective, or model that another entity is based on, organized around, or chiefly concerned with.
-
D.
focusPosition
Indicates the spatial or logical position at which attention, concentration, or processing is currently directed within a given context.
-
E.
focusShift
Indicates a change in attention or emphasis from one entity or topic to another.
- 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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bcbef1e481909fb49427dbd76460 |
completed | April 29, 2026, 8:09 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:12 p.m.