Triple
T10996528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quran 49:13 |
E259883
|
entity |
| Predicate | openingAddress |
P96132
|
FINISHED |
| Object | O mankind |
—
|
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: O mankind | Statement: [Quran 49:13, openingAddress, O mankind]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingAddress Context triple: [Quran 49:13, openingAddress, O mankind]
-
A.
openingTo
Indicates that one entity serves as an entrance, access point, or passage leading into or toward another entity.
-
B.
openingByOffice
Indicates that an office or administrative unit is responsible for initiating or formally opening something (such as a case, process, or record).
-
C.
openingStyle
chosen
Indicates how something is initially presented, introduced, or begun in terms of manner, format, or approach.
-
D.
openingDetail
Indicates the specific manner, context, or characteristics of how an opening (such as a beginning, start, or initial access point) occurs or is carried out between entities.
-
E.
openingInvocation
Indicates the act of formally beginning an event, process, or sequence through an initiating statement, action, or call.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d795d6572c8190a47d68483863ad7a |
completed | April 9, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_69d72e93ac648190b46c5d12bf3eb1e9 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.