Triple
T32124152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Butterfly Room |
E820453
|
entity |
| Predicate | targetAgeGroupInStory |
P13483
|
FINISHED |
| Object | older children |
—
|
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: older children | Statement: [Butterfly Room, targetAgeGroupInStory, older children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetAgeGroupInStory Context triple: [Butterfly Room, targetAgeGroupInStory, older children]
-
A.
intendedForAgeGroup
Indicates that something is designed, suitable, or targeted for use by a specific age group.
-
B.
hasProtagonistAgeRange
Indicates that a work’s main character falls within a specified age range.
-
C.
childInStory
Indicates that one entity is a child character who appears within the narrative context of the other entity (a story).
-
D.
intendedAudienceBeyondStory
Indicates that the work is created with an audience in mind that extends beyond the immediate or in-story participants, addressing external or broader viewers/readers.
-
E.
portraysAgeGroup
chosen
Indicates that one entity depicts or represents another entity as belonging to a particular 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
Created at: May 1, 2026, 12:29 a.m.