Triple
T12854493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gurpurab |
E307412
|
entity |
| Predicate | coreThemes |
P100509
|
FINISHED |
| Object | devotion to the Gurus |
—
|
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: devotion to the Gurus | Statement: [Gurpurab, coreThemes, devotion to the Gurus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreThemes Context triple: [Gurpurab, coreThemes, devotion to the Gurus]
-
A.
themeExamples
Indicates that the related entity serves as an example or illustration of the theme expressed by the subject.
-
B.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
C.
themeKey
chosen
Indicates that one entity serves as the primary subject, topic, or thematic focus associated with another entity.
-
D.
featuresThemeType
Indicates that something (such as a work, event, or item) has or is characterized by a particular type of theme.
-
E.
editorialTheme
Indicates a relationship where an editorial work is associated with a specific overarching theme or subject focus that guides its content and presentation.
- 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_69d7bdf5e7cc8190be357278bc5ba3bb |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa3002881908000357b1f95a3ac |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:37 p.m.