Triple
T10044715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawamim surahs |
E207585
|
entity |
| Predicate | areRevealedIn |
P38401
|
FINISHED |
| Object | Meccan period (predominantly) |
—
|
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: Meccan period (predominantly) | Statement: [Hawamim surahs, areRevealedIn, Meccan period (predominantly)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areRevealedIn Context triple: [Hawamim surahs, areRevealedIn, Meccan period (predominantly)]
-
A.
isRevealedIn
chosen
Indicates that something becomes known, disclosed, or made apparent within a particular context, medium, or situation.
-
B.
isRevealedTo
Indicates that previously hidden or unknown information becomes known to a specific entity or group.
-
C.
revealedAfter
Indicates that one piece of information, event, or state becomes known or disclosed only subsequent to another specified point in time or condition.
-
D.
revealedBefore
Indicates that one entity becomes known, disclosed, or made apparent earlier in time than another entity.
-
E.
revealedSecretOf
Indicates that one entity has disclosed or exposed confidential or previously unknown information belonging to another entity.
- 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_69ca835ad0608190b7c80b292da004f5 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcf62ecf081909c055171b78a883a |
completed | April 2, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:56 p.m.