Triple
T21527455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oliver Quick |
E531131
|
entity |
| Predicate | hasOnScreenAgeRange |
P122542
|
FINISHED |
| Object | late teens to early twenties |
—
|
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: late teens to early twenties | Statement: [Oliver Quick, hasOnScreenAgeRange, late teens to early twenties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnScreenAgeRange Context triple: [Oliver Quick, hasOnScreenAgeRange, late teens to early twenties]
-
A.
hasApproximateAgeRange
chosen
Indicates that one entity is associated with another entity representing an estimated or non-exact span of ages.
-
B.
supportsAgeRange
Indicates that one entity is compatible with, valid for, or designed to accommodate a specified range of ages.
-
C.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of another entity.
-
D.
hasProtagonistAgeRange
Indicates that a work’s main character falls within a specified age range.
-
E.
hasAgeGuidelines
Indicates that there are specified age-related rules or recommendations governing how something should be accessed, used, or engaged with.
- 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_69e0c45e5b8881908ac18fc2f493b114 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee88522e948190b9fa5a3587f32eae |
completed | April 26, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:26 p.m.