Triple
T38160403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zapfino Arabic |
E953000
|
entity |
| Predicate | supportsContextualAlternates |
P46158
|
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, supportsContextualAlternates, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsContextualAlternates Context triple: [Zapfino Arabic, supportsContextualAlternates, yes]
-
A.
hasAlternativeContext
chosen
Indicates that something is associated with an additional or different contextual setting or interpretation beyond its primary one.
-
B.
alsoSupports
Indicates that an entity, in addition to its primary or previously stated function, provides support for another entity, feature, or activity.
-
C.
isAlternativeTo
Indicates that one entity can serve as a substitute or different option in place of another.
-
D.
hasAlternativeReferent
Indicates that an entity can also be referred to or identified by an alternative name, label, or reference.
-
E.
hasNeutralAlternative
Indicates that something has an alternative option that is neutral in effect, stance, or value compared to the original.
- 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_69f76f0b93c48190a117319ab3a9f282 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.