Triple
T32642981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Curry |
E834528
|
entity |
| Predicate | perceptionByReaders |
P95128
|
FINISHED |
| Object | humorous character |
—
|
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: humorous character | Statement: [Mr. Curry, perceptionByReaders, humorous character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perceptionByReaders Context triple: [Mr. Curry, perceptionByReaders, humorous character]
-
A.
readerReception
chosen
Indicates how readers interpret, respond to, or are affected by a particular text or work.
-
B.
readership
Indicates the relationship in which one party reads, follows, or is the audience for the written or published work of another.
-
C.
influencedPerceptionOf
Indicates that one entity has affected, shaped, or altered how another entity is perceived or understood.
-
D.
perceptionByStudents
Indicates how something (such as a concept, event, or object) is viewed, interpreted, or understood by students.
-
E.
readerExperience
Indicates the level or nature of engagement, understanding, or impact that a text or content has on its reader.
- 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_69f3492e773c81908afc10651e46cad3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:07 a.m.