Triple
T33947278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicholas Peterson |
E870326
|
entity |
| Predicate | typicalStoryFunction |
P7328
|
FINISHED |
| Object | source of humor |
—
|
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: source of humor | Statement: [Nicholas Peterson, typicalStoryFunction, source of humor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStoryFunction Context triple: [Nicholas Peterson, typicalStoryFunction, source of humor]
-
A.
storyFunction
chosen
Indicates that one entity serves a particular narrative role or function within the story structure of another entity.
-
B.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
C.
storyTitle
Indicates that one entity is the title assigned to a story associated with another entity.
-
D.
firstRegularStory
Indicates that an entity is the earliest or primary standard (non-special) story associated with another entity in a sequence or collection.
-
E.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
- 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:49 a.m.