Triple
T3403871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surah Al-Asr |
E71722
|
entity |
| Predicate | containsKeyConcept |
P531
|
FINISHED |
| Object | iman (faith) |
—
|
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: iman (faith) | Statement: [Surah Al-Asr, containsKeyConcept, iman (faith)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsKeyConcept Context triple: [Surah Al-Asr, containsKeyConcept, iman (faith)]
-
A.
hasConcept
chosen
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
B.
hasCriticalConcept
Indicates that one entity includes, depends on, or is defined by a key concept that is essential to understanding or functioning of another entity.
-
C.
hasSubConcept
Indicates that one concept is a more specific, subordinate, or narrower idea within the scope of another, more general concept.
-
D.
introducedConcept
Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
-
E.
partOfConcept
Indicates that one concept is a constituent or component of a larger, more encompassing concept.
- 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_69ad85aac4808190a092c9cc8911f584 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb8e8ea848190b4ac167f1aba8ebd |
completed | March 8, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69adadfa73ac8190a163f93e88d217f8 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.