Triple
T12346440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walter Hobbs |
E294366
|
entity |
| Predicate | notableTraitInPlot |
P21469
|
FINISHED |
| Object | is on Santa's naughty list |
—
|
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: is on Santa's naughty list | Statement: [Walter Hobbs, notableTraitInPlot, is on Santa's naughty list]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTraitInPlot Context triple: [Walter Hobbs, notableTraitInPlot, is on Santa's naughty list]
-
A.
notableWorkInPlot
Indicates that a work is prominently featured or plays a significant role within the plot of another work.
-
B.
notableTraitInMarvel
Indicates that a particular trait or characteristic is especially prominent or noteworthy within the Marvel universe.
-
C.
protagonistCharacteristic
chosen
Indicates that a characteristic, trait, or defining quality is attributed to the protagonist in a narrative or scenario.
-
D.
notableFeat
Indicates that an entity is recognized for having achieved or performed a particularly significant or distinguished feat.
-
E.
notableFeatureOn
Indicates that one entity is a prominent or distinguishing feature located on or part of another 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f7a4a448190aa70d66dc2f406c1 |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ecb5efc819086a3530282278bb1 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.