Triple
T7593466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Musa and Khidr |
E179796
|
entity |
| Predicate | endsAtVerse |
P45883
|
FINISHED |
| Object | 82 |
—
|
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: 82 | Statement: [Musa and Khidr, endsAtVerse, 82]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endsAtVerse Context triple: [Musa and Khidr, endsAtVerse, 82]
-
A.
closingVerse
Indicates that one entity serves as the final or concluding verse of another entity, such as a song, poem, or hymn.
-
B.
endOf
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
-
C.
endedWith
Indicates that one event, process, or state concluded with or was finalized by another specified event, condition, or outcome.
-
D.
hasEnding
Indicates that one entity concludes with, or terminates in, another entity (such as a specific substring, segment, or final component).
-
E.
scripturalReferenceEnd
chosen
Indicates the ending position or boundary of a cited scriptural passage within a text or reference.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9bab3a08190a2c36b2c72a1de25 |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:53 p.m.