Triple
T5628968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Family of Imran |
E147787
|
entity |
| Predicate | containsKeyVerse |
P28117
|
FINISHED |
| Object | 3:18 declaration of God’s oneness |
—
|
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: 3:18 declaration of God’s oneness | Statement: [The Family of Imran, containsKeyVerse, 3:18 declaration of God’s oneness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsKeyVerse Context triple: [The Family of Imran, containsKeyVerse, 3:18 declaration of God’s oneness]
-
A.
containsVerse
chosen
Indicates that one entity (typically a text or collection) includes a specific verse as part of its content.
-
B.
hasVersesBy
Indicates a relationship where a work, such as a song or poem, contains verses authored or written by a specific creator.
-
C.
keyVerse
Indicates that one verse is designated as the central or most thematically important verse in relation to a text, passage, or concept.
-
D.
hasVerseRange
Indicates a relationship where a text or passage is associated with a specific contiguous range of verses it spans.
-
E.
hasVerseCount
Indicates that an entity (such as a text or section) is associated with a specific number of verses it contains.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0223b1e54819099fe5fc84ed17a88 |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.