Triple
T25761144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Young Democrats |
E648741
|
entity |
| Predicate | ageRangeRepresented |
P125218
|
FINISHED |
| Object | young adults |
—
|
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: young adults | Statement: [California Young Democrats, ageRangeRepresented, young adults]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageRangeRepresented Context triple: [California Young Democrats, ageRangeRepresented, young adults]
-
A.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
B.
ageRangeUpper
Indicates the maximum age limit that bounds the upper end of an age range associated with an entity or relationship.
-
C.
hasApproximateAgeRange
Indicates that one entity is associated with another entity representing an estimated or non-exact span of ages.
-
D.
ageGroupIndicated
chosen
Indicates that a specific age range or category is identified or assigned to an entity.
-
E.
ageVariants
Indicates that one entity is an alternative form or version of another distinguished specifically by age (e.g., younger/older or different life-stage variants).
- 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fdeef1348190a32e4ae429680b7d |
completed | May 2, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 5:05 a.m.