Triple
T11628331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akal Ustat |
E276330
|
entity |
| Predicate | placeInScripture |
P94954
|
FINISHED |
| Object | part of early sections of Dasam Granth |
—
|
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: part of early sections of Dasam Granth | Statement: [Akal Ustat, placeInScripture, part of early sections of Dasam Granth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeInScripture Context triple: [Akal Ustat, placeInScripture, part of early sections of Dasam Granth]
-
A.
positionInScripture
chosen
Indicates the specific location or ordering of a passage, verse, or element within a scriptural text.
-
B.
positionInBible
Indicates the specific location or order of a passage, verse, or book within the structured sequence of the Bible.
-
C.
inScripture
Indicates that something is mentioned, described, or referenced within a scriptural or sacred text.
-
D.
receivedScripture
Indicates that one entity has been given or accepted a body of sacred or authoritative religious writings from another source.
-
E.
hasScripture
Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a1259cd08190a75eeacb5e39b858 |
completed | April 10, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:39 p.m.