Triple
T13168594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhailo songs |
E312915
|
entity |
| Predicate | ageGroupInvolved |
P108861
|
FINISHED |
| Object | multi-generational participation |
—
|
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: multi-generational participation | Statement: [Bhailo songs, ageGroupInvolved, multi-generational participation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageGroupInvolved Context triple: [Bhailo songs, ageGroupInvolved, multi-generational participation]
-
A.
ageGroup
Indicates the categorical age range or bracket to which an entity belongs.
-
B.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
C.
ageGroupRole
Indicates the role or function an entity has within a specific age group classification.
-
D.
ageGroupSystem
Indicates a classification relationship where entities are grouped according to a defined system of age-based categories.
-
E.
ageGroupStructure
Indicates how a population or set of entities is distributed across different age groups or age categories.
- 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98ceeb22c8190a6be666031d9e5a4 |
completed | April 10, 2026, 11:51 p.m. |
Created at: April 9, 2026, 9:13 p.m.