Triple
T10258602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 42-line Bible |
E240536
|
entity |
| Predicate | survivingCopiesType |
P59261
|
FINISHED |
| Object | complete copies |
—
|
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: complete copies | Statement: [42-line Bible, survivingCopiesType, complete copies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivingCopiesType Context triple: [42-line Bible, survivingCopiesType, complete copies]
-
A.
survivingCopiesOfFirstEdition
chosen
Indicates that the subject has or is associated with copies that remain extant from the first edition of a work.
-
B.
hasSurvivingOriginals
Indicates that some of the original instances or versions of an entity still exist and have not been lost, destroyed, or replaced.
-
C.
haveApproximateCompleteCopies
Indicates that one entity possesses nearly full, but not necessarily perfectly exact, copies of another entity.
-
D.
isCopiedBy
Indicates that an entity serves as the source from which another entity is duplicated or reproduced.
-
E.
supportsDataReplicationFactor
Indicates that an entity enables, configures, or is compatible with a specified data replication factor for storing or duplicating data.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2b5853081909cd0397e08a0f44d |
completed | April 7, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69d4d1edae6881909a65201b8e51ea0a |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:31 a.m.