Triple
T2182554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surah An-Najm |
E49077
|
entity |
| Predicate | openingOath |
P1202
|
FINISHED |
| Object | By the star when it descends |
—
|
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: By the star when it descends | Statement: [Surah An-Najm, openingOath, By the star when it descends]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingOath Context triple: [Surah An-Najm, openingOath, By the star when it descends]
-
A.
openingInvocation
Indicates the act of formally beginning an event, process, or sequence through an initiating statement, action, or call.
-
B.
oathTakenBy
Indicates that an oath or formal promise has been made by a specific entity.
-
C.
oath
chosen
Indicates a formal, binding promise or pledge made by one party to uphold certain duties, truths, or obligations, often under conditions of solemnity or authority.
-
D.
openingKeynoteBy
Indicates that a particular person or entity is delivering the opening keynote for an event or conference.
-
E.
openingWorkOf
Indicates that one work serves as the first or introductory piece in relation to another work, such as the opening item in a sequence or collection.
- 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_69a88aa72d348190a9544bb5b8a4e71d |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc4358fc88190a6f556c2de9fef8c |
completed | March 7, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69abbda0ec948190be88c1243d81a423 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.