Triple
T10044690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawamim surahs |
E207585
|
entity |
| Predicate | areConsecutive |
P63984
|
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: [Hawamim surahs, areConsecutive, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areConsecutive Context triple: [Hawamim surahs, areConsecutive, true]
-
A.
hasContinuousSequence
Indicates that there exists an unbroken, ordered sequence or range connecting the related entities without gaps.
-
B.
consecutiveStartsRank
chosen
Indicates that one entity’s starting position in an ordered sequence immediately follows another entity’s starting position, with no gap between them.
-
C.
maximumConsecutiveTerms
Indicates the greatest number of terms that can occur in an unbroken, continuous sequence within a given context or structure.
-
D.
isSeriesOf
Indicates that one entity is a sequence or set of related items that collectively form a series associated with another entity.
-
E.
successiveIndividuals
Indicates that one individual directly follows another in a sequence or ordered progression.
- 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.