Triple
T25868568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ar-Rahim |
E651686
|
entity |
| Predicate | calligraphyTradition |
P33125
|
FINISHED |
| Object | Islamic calligraphy |
—
|
NE NERFINISHED |
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 calligraphy | Statement: [Ar-Rahim, calligraphyTradition, Islamic calligraphy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calligraphyTradition Context triple: [Ar-Rahim, calligraphyTradition, Islamic calligraphy]
-
A.
calligraphicUse
Indicates that one entity uses or applies another entity specifically for calligraphic purposes or in the practice of calligraphy.
-
B.
paintingTradition
Indicates a stylistic or cultural school of painting to which an artwork or artist belongs.
-
C.
traditionalArtForm
chosen
Indicates that something is an established artistic practice or style that has been handed down through cultural or historical tradition.
-
D.
drawsFromTradition
Indicates that something is influenced by, incorporates, or builds upon established traditions or traditional practices.
-
E.
hasCalligraphy
Indicates that an entity possesses or is associated with calligraphy, such as having calligraphic writing, decoration, or stylistic features.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f602da6e808190a3ff3786b1b07c65 |
completed | May 2, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69f4939148dc81908706cec7d85291bc |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 8:08 a.m.