Triple
T34292011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gurdwara Mal Ji Sahib |
E879915
|
entity |
| Predicate | accessPractice |
P182792
|
FINISHED |
| Object | head covering required inside shrine |
—
|
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: head covering required inside shrine | Statement: [Gurdwara Mal Ji Sahib, accessPractice, head covering required inside shrine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessPractice Context triple: [Gurdwara Mal Ji Sahib, accessPractice, head covering required inside shrine]
-
A.
accessIs
Indicates that one entity has the ability, permission, or means to reach, use, or interact with another entity or resource.
-
B.
accessMission
Indicates that an entity is permitted to enter, use, or interact with a specific mission or mission-related resources.
-
C.
accessProvides
Indicates that one entity grants or enables the ability to use, enter, or retrieve another entity or resource.
-
D.
accessRight
Indicates that one entity has a specified permission or level of authorization to use, view, or interact with another entity or resource.
-
E.
accessMethod
Indicates the means, process, or technique by which something is accessed, retrieved, or made available.
- 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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7908ec35881909a42f954fb9fa16e |
completed | May 3, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78fd3fd888190b7db0b563f298585 |
completed | May 3, 2026, 6:11 p.m. |
Created at: May 1, 2026, 1:57 a.m.