Triple
T19659768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindu Swayamsevak Sangh |
E472049
|
entity |
| Predicate | isVolunteerRun |
P96096
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hindu Swayamsevak Sangh, isVolunteerRun, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isVolunteerRun Context triple: [Hindu Swayamsevak Sangh, isVolunteerRun, true]
-
A.
volunteerRunLine
chosen
Indicates that a particular service, organization, or operation is managed and carried out primarily by volunteers rather than paid staff.
-
B.
hasVolunteerStatus
Indicates that an entity holds a particular volunteer-related status or role within a specified context.
-
C.
isCommunityRun
Indicates that something is managed, operated, or governed collectively by members of a community rather than by an external or centralized authority.
-
D.
hasVolunteerProgram
Indicates that an organization or entity offers an organized program through which individuals can volunteer their time or services.
-
E.
volunteeredFor
Indicates that an entity willingly offered their time or services to support or participate in an activity, cause, or organization.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6414993ac8190b6da3702b1924b24 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:45 p.m.