Triple
T18120885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mass-Observation |
E433726
|
entity |
| Predicate | usedVolunteerContributors |
P118627
|
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: [Mass-Observation, usedVolunteerContributors, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedVolunteerContributors Context triple: [Mass-Observation, usedVolunteerContributors, yes]
-
A.
volunteersFrom
Indicates that one entity serves as a volunteer originating from, or affiliated with, another entity (such as an organization, group, or location).
-
B.
volunteeredFor
Indicates that an entity willingly offered their time or services to support or participate in an activity, cause, or organization.
-
C.
receivedVolunteersFrom
Indicates that one entity accepted or was provided with volunteers originating from another entity.
-
D.
volunteerLabel
Indicates that an entity is identified or tagged as a volunteer in relation to another entity or context.
-
E.
hasVolunteerParticipation
chosen
Indicates that an entity is involved in or benefits from activities performed by volunteers.
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddea61bc8190af4b3efa2596b632 |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.