Triple
T35941219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oweiss Prize for Arabic Narrative |
E1039446
|
entity |
| Predicate | targetCreators |
P10541
|
FINISHED |
| Object | Arabic-language authors |
—
|
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: Arabic-language authors | Statement: [Oweiss Prize for Arabic Narrative, targetCreators, Arabic-language authors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetCreators Context triple: [Oweiss Prize for Arabic Narrative, targetCreators, Arabic-language authors]
-
A.
positionOnCreators
Indicates that one entity holds a specific stance, opinion, or evaluative position regarding the creators of another entity.
-
B.
targetsUseCase
Indicates that one entity is aimed at or designed to address a particular use case associated with another entity.
-
C.
targetsGroup
chosen
Indicates that an action, influence, or effect is directed toward a specific group as its intended recipient or focus.
-
D.
targetDevelopers
Indicates that something is specifically aimed at, intended for, or directed toward developers as its primary audience or users.
-
E.
usedByCreators
Indicates that something is utilized or employed by creators in their work or activities.
- 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_69f76e24bbd0819096b837d35371639a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: May 3, 2026, 4:07 p.m.