Triple
T8379369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arabic Supplement |
E197651
|
entity |
| Predicate | blockCategory |
P87
|
FINISHED |
| Object | Alphabetic |
—
|
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: Alphabetic | Statement: [Arabic Supplement, blockCategory, Alphabetic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blockCategory Context triple: [Arabic Supplement, blockCategory, Alphabetic]
-
A.
blockType
Indicates that one entity is classified as a specific type or category of block in relation to another entity.
-
B.
programmingBlock
Indicates a relationship where one entity is a defined segment or unit of programming logic (such as a code block or script section) associated with or contained within another entity.
-
C.
scriptCategory
Indicates the classification or type of script to which an entity (such as a written work, code, or performance text) belongs.
-
D.
category
chosen
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
E.
textCategory
Indicates that a piece of text belongs to or is classified under a particular category or type.
- 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_69ca82f64c188190af4e1608036b865d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80c3dc1881908081c6a2829deb5a |
completed | March 31, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69cb70cfe82881909fe374ba52649e84 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:02 p.m.