Triple
T33051550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | طور |
E845735
|
entity |
| Predicate | hasQuranicOathType |
P176097
|
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: [طور, hasQuranicOathType, قسم بمكان مقدس]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQuranicOathType Context triple: [طور, hasQuranicOathType, قسم بمكان مقدس]
-
A.
containsOathBy
Indicates that one entity (such as a text, document, or statement) includes or features an oath made by another entity.
-
B.
hasOathTo
Indicates a relationship in which one entity is bound by an oath or sworn commitment to another entity.
-
C.
containsOaths
Indicates that one entity (typically a text or statement) includes one or more oaths, vows, or sworn declarations.
-
D.
swornByInQuran
chosen
Indicates that something is mentioned in the Quran as an object by which an oath is sworn.
-
E.
hasSwornType
Indicates that one entity has formally pledged or committed to a specific type, category, or classification of something.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:24 a.m.