Triple
T10612630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japji Sahib |
E276042
|
entity |
| Predicate | placeInPractice |
P12146
|
FINISHED |
| Object | memorized by many Sikhs |
—
|
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: memorized by many Sikhs | Statement: [Japji Sahib, placeInPractice, memorized by many Sikhs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeInPractice Context triple: [Japji Sahib, placeInPractice, memorized by many Sikhs]
-
A.
usedInPractice
Indicates that something is actually applied or implemented in real-world practice rather than just being theoretical or proposed.
-
B.
describedPractice
Indicates that one entity has provided a description or explanation of a particular practice associated with another entity.
-
C.
typicalPractice
chosen
Indicates that an action, behavior, or method is commonly or customarily done in a given context or by a given group.
-
D.
practice
Indicates that an entity regularly performs an activity or skill, typically to improve proficiency or maintain competence.
-
E.
primaryFunctionInPractice
Indicates that an entity serves as the main or most important function or role within a given practical context or real-world usage.
- 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_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. |
Created at: April 8, 2026, 7:33 p.m.