Triple
T19728263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Children of the Queen's Revels |
E473782
|
entity |
| Predicate | typicalCastAgeRange |
P27858
|
FINISHED |
| Object | boys and young adolescents |
—
|
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: boys and young adolescents | Statement: [Children of the Queen's Revels, typicalCastAgeRange, boys and young adolescents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCastAgeRange Context triple: [Children of the Queen's Revels, typicalCastAgeRange, boys and young adolescents]
-
A.
typicalAgeRangeOfWinners
Indicates the usual age range within which the winners of a particular competition, award, or event typically fall.
-
B.
hasProtagonistAgeRange
Indicates that a work’s main character falls within a specified age range.
-
C.
typicalCast
chosen
Indicates that the associated entities form the usual or characteristic cast of characters commonly appearing in a given work or type of work.
-
D.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
E.
typicalAgeRangeOfPlayers
Indicates the usual age range of people who typically play or participate in 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e649fa1bc481908a9e7cf4fc52f75c |
completed | April 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:47 p.m.