Triple
T14550110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Alaq |
E341392
|
entity |
| Predicate | mentionsCreationFrom |
P53571
|
FINISHED |
| Object | a clinging clot |
—
|
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: a clinging clot | Statement: [Al-Alaq, mentionsCreationFrom, a clinging clot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionsCreationFrom Context triple: [Al-Alaq, mentionsCreationFrom, a clinging clot]
-
A.
mentionsCreationOf
Indicates that one entity explicitly refers to or discusses the bringing into existence or origination of another entity.
-
B.
titleCreatedFrom
chosen
Indicates that a title is derived or generated from another source, such as an existing entity, text, or identifier.
-
C.
mentionedSince
Indicates that one entity has been mentioned or referred to continuously or at least once from a specified point in time onward.
-
D.
hasCreation
Indicates a relationship where one entity is the creator or originator of another entity.
-
E.
createdUnder
Indicates that something was created during the time period or within the authority, rules, or conditions defined by another entity or context.
- 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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb2ed2b4c8190945bd26531c71f1f |
completed | April 14, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:23 a.m.