Triple
T10612674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ik Onkar |
E276043
|
entity |
| Predicate | positionInScripture |
P94954
|
FINISHED |
| Object | opening formula of Sikh scripture |
—
|
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: opening formula of Sikh scripture | Statement: [Ik Onkar, positionInScripture, opening formula of Sikh scripture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInScripture Context triple: [Ik Onkar, positionInScripture, opening formula of Sikh scripture]
-
A.
positionInBible
Indicates the specific location or order of a passage, verse, or book within the structured sequence of the Bible.
-
B.
scripturalReference
Indicates that one entity cites, alludes to, or is based on a specific passage or portion of a scriptural text found in another entity.
-
C.
positionAmongGospels
Indicates the numerical order or placement of a given gospel within the sequence of all gospels.
-
D.
inScripture
Indicates that something is mentioned, described, or referenced within a scriptural or sacred text.
-
E.
receivedScripture
Indicates that one entity has been given or accepted a body of sacred or authoritative religious writings from another source.
- F. None of above. chosen
Provenance (4 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df5baf94819097b14a73af058f35 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7a223c8190854409d76368f3e8 |
completed | April 8, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69d6df463ea8819091d6683e476b4f21 |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 7:33 p.m.