Triple
T29142562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bullwinkle and Rocky |
E738675
|
entity |
| Predicate | featuresMainCharacter |
P93957
|
FINISHED |
| Object | Rocket J. Squirrel |
—
|
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: Rocket J. Squirrel | Statement: [Bullwinkle and Rocky, featuresMainCharacter, Rocket J. Squirrel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresMainCharacter Context triple: [Bullwinkle and Rocky, featuresMainCharacter, Rocket J. Squirrel]
-
A.
featuresCharacterWith
chosen
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
-
B.
featuresCharacterRole
Indicates that a work includes a character appearing in a specific narrative or functional role.
-
C.
featuresCharacterRescue
Indicates that a work includes a scene or storyline in which one character rescues or saves another.
-
D.
protagonistCharacteristic
Indicates that a characteristic, trait, or defining quality is attributed to the protagonist in a narrative or scenario.
-
E.
featuresReturningCharacterFrom
Indicates that a work includes the reappearance of a character who previously appeared in the referenced source work.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
Created at: April 28, 2026, 11:37 a.m.