Triple
T10018439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Library of Ashurbanipal |
E199554
|
entity |
| Predicate | collectionSizeEstimate |
P425
|
FINISHED |
| Object | over 30,000 tablets and fragments |
—
|
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: over 30,000 tablets and fragments | Statement: [Library of Ashurbanipal, collectionSizeEstimate, over 30,000 tablets and fragments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectionSizeEstimate Context triple: [Library of Ashurbanipal, collectionSizeEstimate, over 30,000 tablets and fragments]
-
A.
collectionSize
chosen
Indicates the total number of items contained within a specified collection.
-
B.
mineCountApproximate
Indicates that the number of mines associated with an entity is estimated or roughly counted rather than known exactly.
-
C.
estimatedMemberCount
Indicates the approximate or predicted number of members associated with an entity.
-
D.
hasApproximateMemberCount
Indicates that an entity is associated with a group or collection for which only an estimated or non-exact number of members is known.
-
E.
hasApproximateBrickCount
Indicates that an entity is associated with an estimated or non-exact number of bricks.
- 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_69ca8315a1a08190ab310f25620f362b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd4de1588190a89ed575cff0b8c9 |
completed | April 2, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69cd4b7cd4208190b2253583ee2f892c |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:53 p.m.