Triple
T594810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bibliotheca Alexandrina |
E17356
|
entity |
| Predicate | shelfCapacity |
P1931
|
FINISHED |
| Object | about 8 million books |
—
|
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 8 million books | Statement: [Bibliotheca Alexandrina, shelfCapacity, about 8 million books]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shelfCapacity Context triple: [Bibliotheca Alexandrina, shelfCapacity, about 8 million books]
-
A.
cabinet
Indicates that one entity serves as a cabinet (a storage or enclosure unit) for another entity.
-
B.
typicalCapacity
chosen
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
C.
storageFacility
Indicates a relationship where one entity serves as a place or facility used to store another entity or its items.
-
D.
hasCabinet
Indicates that one entity possesses, includes, or is equipped with a cabinet associated with it.
-
E.
cargoHoldHeight
Indicates the vertical interior dimension or clearance height of a cargo hold space.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bd280ac8190b6a530ce73da85c8 |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494ceeb7881909a91ed1a35d5bf0a |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.