Triple
T10258598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 42-line Bible |
E240536
|
entity |
| Predicate | hasApproximateOriginalEditionSize |
P10552
|
FINISHED |
| Object | about 180 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: about 180 copies | Statement: [42-line Bible, hasApproximateOriginalEditionSize, about 180 copies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateOriginalEditionSize Context triple: [42-line Bible, hasApproximateOriginalEditionSize, about 180 copies]
-
A.
hasEstimatedOriginalVolume
chosen
Indicates that an entity is associated with an approximate or calculated value for its original volume.
-
B.
hasOriginalVersion
Indicates that one entity is the original or initial version from which another entity is derived or adapted.
-
C.
approximateDistancePerEdition
Indicates the estimated distance associated with each individual edition or version of something, typically averaged or approximated per edition.
-
D.
approximateSize
Indicates that one entity has a size that is roughly or approximately equal to the size of another entity.
-
E.
hasDifferentEditions
Indicates that an entity exists in multiple distinct versions or editions that differ in some characteristics.
- 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.