Triple
T38160415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zapfino Arabic |
E953000
|
entity |
| Predicate | hasMultipleGlyphAlternates |
P198207
|
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, hasMultipleGlyphAlternates, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleGlyphAlternates Context triple: [Zapfino Arabic, hasMultipleGlyphAlternates, yes]
-
A.
hasGlyphsFor
Indicates that one entity provides or contains the necessary glyphs or visual symbols to represent another entity.
-
B.
hasLigatures
Indicates that one writing system, font, or text includes combined character forms (ligatures) that join two or more individual glyphs into a single symbol.
-
C.
hasAlternativeSpacing
Indicates that an entity is associated with one or more alternative ways of spacing its characters or components compared to a primary or standard form.
-
D.
hasGlyphRepertoireSize
Indicates the number of distinct glyphs included in an entity’s glyph repertoire.
-
E.
hasAlternativeMultiplierChoice
Indicates that an entity is associated with one or more alternative options for a multiplier that can be chosen instead of a default value.
- 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_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
| PDg | Predicate description generation | batch_69fed098328c819085979de6b179b378 |
completed | May 9, 2026, 6:13 a.m. |
Created at: May 3, 2026, 4:21 p.m.