Triple
T23872349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | And the glory of the Lord |
E592760
|
entity |
| Predicate | originalTextVersion |
P154269
|
FINISHED |
| Object | King James Version |
—
|
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: King James Version | Statement: [And the glory of the Lord, originalTextVersion, King James Version]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalTextVersion Context triple: [And the glory of the Lord, originalTextVersion, King James Version]
-
A.
originalText
Indicates that one text is the initial, unmodified version from which other versions, translations, or representations are derived.
-
B.
originalTextStatus
Indicates the relationship between a text and its current state or condition relative to its original, unmodified form.
-
C.
originalTextOn
Indicates that a piece of original text is physically or logically located on a particular medium, surface, or object.
-
D.
originalVersionStyle
Indicates that one entity represents the stylistic form or manner of expression used in the original version of another entity.
-
E.
originalTextLanguage
Indicates the language in which a text was originally written or created before any translation or adaptation.
- 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cbfed81881909905f71377f759b1 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:14 p.m.