Triple
T29935293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sainya Seva Medal |
E760341
|
entity |
| Predicate | claspSystem |
P168276
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sainya Seva Medal, claspSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claspSystem Context triple: [Sainya Seva Medal, claspSystem, yes]
-
A.
claspIndicates
Indicates a relationship where one entity grasps, holds, or fastens onto another, typically in a secure or enclosing manner.
-
B.
claspPolicy
Indicates that an entity enforces or is governed by a specific CLASP (or similar) security or access control policy.
-
C.
logicSystem
Indicates a relationship where an entity is associated with, defined within, or governed by a particular logical framework or system of formal reasoning.
-
D.
claspForAdditionalService
Indicates that one entity serves as a clasp or fastening component intended to support or enable an additional service or function for another entity.
-
E.
clase
Indicates a classification or type relationship, where one entity is categorized as belonging to a particular class or category defined by another entity.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f677d413c081908203059402081897 |
completed | May 2, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:20 p.m.