Triple
T28326895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Popples |
E717432
|
entity |
| Predicate | fictionalTrait |
P151325
|
FINISHED |
| Object | mischievous behavior |
—
|
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: mischievous behavior | Statement: [Popples, fictionalTrait, mischievous behavior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalTrait Context triple: [Popples, fictionalTrait, mischievous behavior]
-
A.
notableTraitInFiction
chosen
Indicates that a particular trait, characteristic, or quality is especially prominent or defining for an entity within fictional works.
-
B.
comicTrait
Indicates that an entity possesses a humorous or comedic characteristic, quality, or behavior.
-
C.
fictionalCharacter
Indicates that one entity is a fictional character that appears within the narrative world of another entity (such as a work, series, or franchise).
-
D.
fictionalSon
Indicates that one entity is portrayed as the son of another entity within a fictional or narrative context.
-
E.
fictionalPersonaOf
Indicates that one entity is a fictional or narrative persona, alter ego, or character representation of another (typically real or primary) entity.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 28, 2026, 12:29 a.m.