Triple
T22508719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lavan (Sikh marriage hymns) |
E556458
|
entity |
| Predicate | fourthVerseFocus |
P49511
|
FINISHED |
| Object | realization of divine presence and bliss |
—
|
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: realization of divine presence and bliss | Statement: [Lavan (Sikh marriage hymns), fourthVerseFocus, realization of divine presence and bliss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fourthVerseFocus Context triple: [Lavan (Sikh marriage hymns), fourthVerseFocus, realization of divine presence and bliss]
-
A.
verse5Focus
Indicates a specific emphasis or central theme highlighted within verse 5 of a text or passage.
-
B.
verse4Focus
chosen
Indicates a specific emphasis or primary thematic focus associated with verse 4 within a structured text or composition.
-
C.
fourthTrack
Indicates that one entity is the fourth track in an ordered sequence of tracks associated with another entity.
-
D.
firstQuatrainFocus
Indicates that the primary thematic or descriptive emphasis of the first quatrain in a poem is on the specified entity or concept.
-
E.
keyOfFourthSong
Indicates the musical key in which the fourth song in a sequence or collection is set.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15d5ebe5881908a22d519128415f2 |
completed | April 29, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:50 p.m.