Triple
T23718546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Preface to the King James Version of the Bible |
E586076
|
entity |
| Predicate | writtenForWork |
P153684
|
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: [Preface to the King James Version of the Bible, writtenForWork, King James Version]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenForWork Context triple: [Preface to the King James Version of the Bible, writtenForWork, King James Version]
-
A.
worksFrom
Indicates that an entity performs its work or duties starting from or based at a specified location or source.
-
B.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
C.
writtenForProduction
Indicates that a work was created specifically for use in a particular production or performance.
-
D.
commentaryWorkFor
Indicates that one entity performs commentary or analysis work on behalf of, or under employment/contract with, another entity.
-
E.
workedFrom
Indicates that an entity was employed or actively engaged in work starting from a specified point in time.
- 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b77d121c8190892d3f8ef3f3156f |
completed | April 29, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15b453da88190889a8d9b21727958 |
completed | April 29, 2026, 1:13 a.m. |
Created at: April 17, 2026, 6:59 p.m.