Triple
T38160412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zapfino Arabic |
E953000
|
entity |
| Predicate | hasCalligraphicInfluence |
P202119
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Zapfino Arabic, hasCalligraphicInfluence, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCalligraphicInfluence Context triple: [Zapfino Arabic, hasCalligraphicInfluence, yes]
-
A.
hasCalligraphy
Indicates that an entity possesses or is associated with calligraphy, such as having calligraphic writing, decoration, or stylistic features.
-
B.
calligraphicUse
Indicates that one entity uses or applies another entity specifically for calligraphic purposes or in the practice of calligraphy.
-
C.
hasCalligraphyLanguage
Indicates that an entity’s calligraphy is written in, or associated with, a particular language.
-
D.
hasLetterforms
Indicates a relationship where one entity possesses or includes specific letterforms as part of its written or typographic representation.
-
E.
isCursive
Indicates that the referenced writing or text is in cursive (joined, flowing handwriting) form.
- F. None of above. chosen
Provenance (4 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_69f76f0b93c48190a117319ab3a9f282 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a005247dba08190acadf962bcefe4a0 |
completed | May 10, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_6a00519029848190a234358dfba45084 |
completed | May 10, 2026, 9:36 a.m. |
| PDg | Predicate description generation | batch_6a00524723408190b0294e87e5cf7715 |
completed | May 10, 2026, 9:39 a.m. |
Created at: May 3, 2026, 4:21 p.m.