Triple
T934789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyndale Bible |
E20170
|
entity |
| Predicate | incompleteWork |
P18162
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tyndale Bible, incompleteWork, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incompleteWork Context triple: [Tyndale Bible, incompleteWork, true]
-
A.
unfinished
chosen
Indicates that an action, process, or state has started but has not yet been completed.
-
B.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
C.
hasWorkBy
Indicates that one entity (such as a collection, exhibition, or publication) includes or contains creative works produced by another entity (such as an artist, author, or creator).
-
D.
firstWork
Indicates that the related work is the earliest or initial work created, published, or produced by the entity in question.
-
E.
secondWork
Indicates that one work is the second in order relative to another work within a sequence or set.
- 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_69a493af3dc48190adb7263e6e445ea1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b363ea5c819098ec1d87f785bad4 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b29b245c8190b143f28b77fede3c |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.