Triple
T27044518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Durr al-Manthur fi al-Tafsir bi'l-Ma'thur |
E684584
|
entity |
| Predicate | volumes |
P2734
|
FINISHED |
| Object | multi-volume work |
—
|
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: multi-volume work | Statement: [Al-Durr al-Manthur fi al-Tafsir bi'l-Ma'thur, volumes, multi-volume work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: volumes Context triple: [Al-Durr al-Manthur fi al-Tafsir bi'l-Ma'thur, volumes, multi-volume work]
-
A.
volume
Indicates the amount of three-dimensional space an entity occupies or contains.
-
B.
volumeOf
Indicates the quantitative three-dimensional space occupied by an entity or contained within an object.
-
C.
numberOfVolumes
chosen
Indicates the total count of separate volumes or parts that make up a multi-volume work or collection.
-
D.
foundInVolume
Indicates that one entity is physically or logically contained within, or occurs in, a specific volume (such as a book volume, data volume, or bounded collection).
-
E.
collectionVolume
Indicates the total physical or spatial amount occupied by a collection, such as its size, capacity, or volume.
- 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_69ef148193c48190bb1a0cfae6a407c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6226f6b0c8190b5d7274e25efd6b6 |
completed | May 2, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:08 a.m.