Triple
T14313436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | سورة التكاثر |
E354892
|
entity |
| Predicate | افتتاحها |
P15511
|
FINISHED |
| Object | ألهاكم التكاثر |
—
|
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: ألهاكم التكاثر | Statement: [سورة التكاثر, افتتاحها, ألهاكم التكاثر]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: افتتاحها Context triple: [سورة التكاثر, افتتاحها, ألهاكم التكاثر]
-
A.
openingTo
Indicates that one entity serves as an entrance, access point, or passage leading into or toward another entity.
-
B.
opens
Indicates that one entity causes or allows another entity (such as an object, space, or resource) to become accessible or no longer closed.
-
C.
openingWorkOf
chosen
Indicates that one work serves as the first or introductory piece in relation to another work, such as the opening item in a sequence or collection.
-
D.
openingDay
Indicates the specific day on which something, typically an event, season, or venue, officially begins or first opens to the public.
-
E.
openedAt
Indicates that an entity began operating, became accessible, or was first made available at a specific time or date.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85b49e5481909b9ffab2d922e284 |
completed | April 14, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:12 a.m.