Triple
T21683286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edmonton Folk Music Festival |
E535164
|
entity |
| Predicate | hasVolunteerCount |
P145437
|
FINISHED |
| Object | over 2000 volunteers |
—
|
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: over 2000 volunteers | Statement: [Edmonton Folk Music Festival, hasVolunteerCount, over 2000 volunteers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVolunteerCount Context triple: [Edmonton Folk Music Festival, hasVolunteerCount, over 2000 volunteers]
-
A.
hasVolunteerStatus
Indicates that an entity holds a particular volunteer-related status or role within a specified context.
-
B.
hasVolunteerBase
Indicates that an entity maintains or relies on a group of volunteers as a foundational support resource.
-
C.
receivedVolunteersFrom
Indicates that one entity accepted or was provided with volunteers originating from another entity.
-
D.
hasAdultVolunteers
Indicates that an entity is associated with one or more adult individuals who volunteer their time or services for it.
-
E.
usesVolunteers
Indicates that an entity relies on or engages volunteers to perform its activities or services.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96c7c6a08190bbd9a89b8a3b921b |
completed | April 27, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69cb4bcbc8190a4fc2d508df107be |
completed | April 20, 2026, 9:37 p.m. |
Created at: April 16, 2026, 6:43 p.m.