Triple
T12849392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quran 69:1–52 |
E307271
|
entity |
| Predicate | isMeccan |
P30310
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Quran 69:1–52, isMeccan, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMeccan Context triple: [Quran 69:1–52, isMeccan, true]
-
A.
isMeccanSurah
chosen
Indicates that a given surah (chapter of the Qur’an) was revealed in Mecca (i.e., is classified as a Meccan surah) rather than in Medina.
-
B.
mecha
Indicates a relationship where an entity is a mechanical robot or piloted machine, typically used as a vehicle, weapon, or tool in a technological or sci‑fi context.
-
C.
isMICFor
Indicates that one entity represents the minimum inhibitory concentration (MIC) value determined for another entity, typically a microorganism or drug.
-
D.
isMechanicalOrElectronic
Indicates that something operates using mechanical components, electronic components, or a combination of both.
-
E.
isCruxOf
Indicates that something is the central, most critical, or decisive element within a situation, argument, or problem.
- 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_69d7bdf5e7cc8190be357278bc5ba3bb |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa3002881908000357b1f95a3ac |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:36 p.m.