Triple
T19400494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tick, Tick... Boom! |
E485307
|
entity |
| Predicate | centralCharacterAgeConcern |
P37051
|
FINISHED |
| Object | turning 30 |
—
|
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: turning 30 | Statement: [Tick, Tick... Boom!, centralCharacterAgeConcern, turning 30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralCharacterAgeConcern Context triple: [Tick, Tick... Boom!, centralCharacterAgeConcern, turning 30]
-
A.
characterAgeDescriptor
Indicates how a character’s age is qualitatively described or categorized (e.g., young, middle-aged, elderly) rather than given as a specific number.
-
B.
protagonistAge
chosen
Indicates the age of the main character or central figure in a narrative or scenario.
-
C.
hasProtagonistAgeRange
Indicates that a work’s main character falls within a specified age range.
-
D.
ageDepictionConsistency
Indicates that the depicted age of an entity is consistent with its known or expected age within the given context.
-
E.
representedAgeLevel
Indicates that one entity corresponds to, or is categorized under, a particular age level or age group.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6257692508190b658928e224d72d7 |
completed | April 20, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:36 p.m.