Triple
T14905180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NYRR 9+1 program |
E360110
|
entity |
| Predicate | volunteerComponent |
P54077
|
FINISHED |
| Object | race-day volunteering |
—
|
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: race-day volunteering | Statement: [NYRR 9+1 program, volunteerComponent, race-day volunteering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: volunteerComponent Context triple: [NYRR 9+1 program, volunteerComponent, race-day volunteering]
-
A.
volunteeredFor
Indicates that an entity willingly offered their time or services to support or participate in an activity, cause, or organization.
-
B.
volunteerLabel
Indicates that an entity is identified or tagged as a volunteer in relation to another entity or context.
-
C.
typeOfVolunteerUnit
Indicates that one entity is a specific kind or category of volunteer unit in relation to another entity.
-
D.
hasVolunteerProgram
Indicates that an organization or entity offers an organized program through which individuals can volunteer their time or services.
-
E.
volunteerRequirement
chosen
Indicates that an entity has a condition or obligation specifying the need for volunteers or volunteer participation.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded60cd5588190b1efecc2b220da69 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:12 a.m.