Triple
T32670588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Service Corps of Retired Executives |
E835279
|
entity |
| Predicate | volunteers |
P138783
|
FINISHED |
| Object | retired executives |
—
|
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: retired executives | Statement: [Service Corps of Retired Executives, volunteers, retired executives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: volunteers Context triple: [Service Corps of Retired Executives, volunteers, retired executives]
-
A.
usesVolunteers
chosen
Indicates that an entity relies on or engages volunteers to perform its activities or services.
-
B.
volunteersFrom
Indicates that one entity serves as a volunteer originating from, or affiliated with, another entity (such as an organization, group, or location).
-
C.
volunteerLabel
Indicates that an entity is identified or tagged as a volunteer in relation to another entity or context.
-
D.
volunteeredFor
Indicates that an entity willingly offered their time or services to support or participate in an activity, cause, or organization.
-
E.
hasVolunteerPersonnelFrom
Indicates that an entity receives or utilizes volunteer personnel supplied by another entity or source.
- 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_69f349303ccc8190a70d0f6e8a21d3fb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c7ac1f288190ab86a6dd0b6491cd |
completed | May 3, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:09 a.m.