Triple
T656825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arabic calligraphy |
E11665
|
entity |
| Predicate | relatedArtForm |
P37
|
FINISHED |
| Object | Islamic geometric patterns |
—
|
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 geometric patterns | Statement: [Arabic calligraphy, relatedArtForm, Islamic geometric patterns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedArtForm Context triple: [Arabic calligraphy, relatedArtForm, Islamic geometric patterns]
-
A.
artMovement
Indicates the artistic movement or style with which an artwork, artist, or cultural work is associated.
-
B.
associatedMusic
Indicates a relationship where one entity is linked to or connected with a piece of music, such as being used by, related to, or thematically tied to that music.
-
C.
hasArtisticDiscipline
Indicates that one entity practices, specializes in, or is associated with a particular artistic discipline or field.
-
D.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
-
E.
artworkType
Indicates the specific category or kind of artwork that characterizes the relationship between the subject and the artwork.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f4e87408190b5276d2b913d0426 |
completed | March 1, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69a49d121cec81909986c91291bb4ca8 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.