Triple
T38160276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palatino Arabic |
E952996
|
entity |
| Predicate | hasOpenTypeFeatures |
P190168
|
FINISHED |
| Object | contextual forms |
—
|
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: contextual forms | Statement: [Palatino Arabic, hasOpenTypeFeatures, contextual forms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpenTypeFeatures Context triple: [Palatino Arabic, hasOpenTypeFeatures, contextual forms]
-
A.
usesOpenTypeFeatures
chosen
Indicates that one entity employs or supports OpenType typographic features in relation to another entity or context.
-
B.
hasFeature
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
C.
hasOpeningType
Indicates that one entity has, features, or is characterized by a particular type or kind of opening.
-
D.
hasTraditionalFeatures
Indicates that something possesses characteristics or attributes commonly associated with established traditions or customary practices.
-
E.
hasOpeningFeature
Indicates that an entity possesses a specific characteristic, element, or attribute related to its opening or entry point.
- 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_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: May 3, 2026, 4:21 p.m.