Triple
T30288461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunday Times Young Writer of the Year Award |
E770302
|
entity |
| Predicate | eligibleAgeLimit |
P99503
|
FINISHED |
| Object | 35 |
—
|
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: 35 | Statement: [Sunday Times Young Writer of the Year Award, eligibleAgeLimit, 35]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibleAgeLimit Context triple: [Sunday Times Young Writer of the Year Award, eligibleAgeLimit, 35]
-
A.
governsAgeEligibility
Indicates that one entity sets or controls the age-related criteria determining another entity’s eligibility for something.
-
B.
ageLimitAppliesAt
Indicates the specific age or point in time at which an age-related restriction or limit becomes effective for an entity.
-
C.
ageLimitType
Indicates the type or category of age restriction that applies to an entity or activity.
-
D.
ageLimitYears
chosen
Indicates the maximum allowed age, expressed in years, for which something is valid, permitted, or applicable.
-
E.
ageConstraint
Indicates a restriction or condition based on the age of an entity relative to a specified threshold or 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 29, 2026, 7:46 p.m.