Triple
T13432639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astan Quds Razavi |
E313648
|
entity |
| Predicate | hasLibraryCollectionType |
P14119
|
FINISHED |
| Object | Islamic manuscripts |
—
|
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: Islamic manuscripts | Statement: [Astan Quds Razavi, hasLibraryCollectionType, Islamic manuscripts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLibraryCollectionType Context triple: [Astan Quds Razavi, hasLibraryCollectionType, Islamic manuscripts]
-
A.
libraryCollectionType
chosen
Indicates the specific category or type of collection that a library maintains or offers (e.g., reference, circulating, digital).
-
B.
hasLibraryHoldings
Indicates that a library possesses or maintains specific items or collections within its holdings.
-
C.
hasLibraryBranch
Indicates that an entity possesses or is associated with one or more library branches as part of its organizational structure or services.
-
D.
hasCollectionType
Indicates that an entity is associated with or organized under a specific type or category of collection.
-
E.
hasDigitalLibrary
Indicates that an entity maintains or provides access to a collection of digital resources or publications.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed41a5481908800033303224adb |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.