Triple
T18330291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Young Artist of the Year |
E439118
|
entity |
| Predicate | typicalAgeRangeOfRecipients |
P2736
|
FINISHED |
| Object | 20s to early 30s |
—
|
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: 20s to early 30s | Statement: [Young Artist of the Year, typicalAgeRangeOfRecipients, 20s to early 30s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAgeRangeOfRecipients Context triple: [Young Artist of the Year, typicalAgeRangeOfRecipients, 20s to early 30s]
-
A.
typicalAge
Indicates the usual or characteristic age associated with an entity, event, or condition.
-
B.
typicalAgeRangeLower
Indicates the minimum age value that typically marks the lower bound of an expected or common age range for something.
-
C.
typicalEligibilityAge
Indicates the usual or standard age at which an entity qualifies for or becomes eligible for a particular status, benefit, or activity.
-
D.
ageRange
chosen
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
E.
servesAgeRange
Indicates that a service, product, or offering is intended for or applicable to entities within a specified age range.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50ec900808190bc4468270e0957c1 |
completed | April 19, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.