Triple
T12540756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Young Adult Science Fiction and Fantasy |
E299830
|
entity |
| Predicate | hasTypicalProtagonistAgeRange |
P2736
|
FINISHED |
| Object | 12–18 |
—
|
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: 12–18 | Statement: [Young Adult Science Fiction and Fantasy, hasTypicalProtagonistAgeRange, 12–18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalProtagonistAgeRange Context triple: [Young Adult Science Fiction and Fantasy, hasTypicalProtagonistAgeRange, 12–18]
-
A.
ageRange
chosen
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
B.
typicalAge
Indicates the usual or characteristic age associated with an entity, event, or condition.
-
C.
fictionalAgeRange
Indicates the span of ages a fictional character or entity is depicted as having within a narrative or fictional context.
-
D.
typicalEligibilityAge
Indicates the usual or standard age at which an entity qualifies for or becomes eligible for a particular status, benefit, or activity.
-
E.
typicalAgeRangeLower
Indicates the minimum age value that typically marks the lower bound of an expected or common age range for something.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d9540d7b788190a0d57b098e90e491 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.