Triple
T28711749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arabic Presentation Forms-A |
E729847
|
entity |
| Predicate | hasGeneralCategoryMix |
P141747
|
FINISHED |
| Object | Letter |
—
|
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: Letter | Statement: [Arabic Presentation Forms-A, hasGeneralCategoryMix, Letter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeneralCategoryMix Context triple: [Arabic Presentation Forms-A, hasGeneralCategoryMix, Letter]
-
A.
hasIceOrMixedGrade
Indicates that a road segment or surface currently has icy conditions or a mixture of ice and other surface states (e.g., wet, slushy, or bare).
-
B.
hasMorphologicalMix
chosen
Indicates that an entity exhibits a combination of different morphological types or structures within a single form or system.
-
C.
hasSpecialCategory
Indicates that an entity is associated with a designated special or exceptional category distinct from its standard classifications.
-
D.
isHeterogeneous
Indicates that the related entities are diverse in type, nature, or composition rather than uniform or identical.
-
E.
hasRemixGenre
Indicates that a work or track has a remix version characterized by a particular musical genre.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 28, 2026, 5:48 a.m.