Triple
T35919981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maqamat al-Hariri |
E1038853
|
entity |
| Predicate | hasIlluminatedManuscripts |
P59202
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Maqamat al-Hariri, hasIlluminatedManuscripts, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIlluminatedManuscripts Context triple: [Maqamat al-Hariri, hasIlluminatedManuscripts, true]
-
A.
earliestManuscripts
Indicates that the related entity (e.g., a text or work) is associated with its earliest known surviving manuscripts or documentary witnesses.
-
B.
notableManuscriptFeature
chosen
Indicates that a manuscript possesses a specific distinguishing characteristic, attribute, or element that is considered noteworthy or significant.
-
C.
notableManuscriptSource
Indicates that one entity serves as a significant or historically important manuscript source for another entity.
-
D.
manuscriptFoundIn
Indicates that a manuscript is discovered or located within a particular place, collection, or context.
-
E.
areManuscriptsOf
Indicates that the subject entities are manuscripts that are versions, copies, or instances of the work represented by the object entity.
- 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_69f76e2320748190b7f5c4750d0cd0d3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaa9ba18819082a9b86a87e82f75 |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:07 p.m.