Triple
T29361942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Charlie Brown Celebration |
E744614
|
entity |
| Predicate | hasFranchiseCharacterGroup |
P47706
|
FINISHED |
| Object | Peanuts gang |
—
|
NE NERFINISHED |
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: Peanuts gang | Statement: [A Charlie Brown Celebration, hasFranchiseCharacterGroup, Peanuts gang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFranchiseCharacterGroup Context triple: [A Charlie Brown Celebration, hasFranchiseCharacterGroup, Peanuts gang]
-
A.
franchiseCharacter
Indicates a relationship where a character belongs to, appears in, or is part of a particular media franchise.
-
B.
hasItemInFranchise
Indicates that an entity possesses or includes a specific item as part of a larger franchise or branded collection.
-
C.
hasProtagonistGroup
Indicates that a narrative work features a central group of characters who collectively serve as the main protagonists.
-
D.
associatedWithCharacterGroup
chosen
Indicates that an entity has a connection or affiliation with a particular group of characters.
-
E.
hasFranchiseProtagonistTrait
Indicates that a protagonist in a franchise possesses a specific recurring trait or characteristic associated with that franchise.
- 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 28, 2026, 2:18 p.m.