Triple
T35067720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Be Sweet |
E1011775
|
entity |
| Predicate | hasProtagonistFocus |
P8706
|
FINISHED |
| Object | Lumpy Space Princess |
E309307
|
NE 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: Lumpy Space Princess | Statement: [Be Sweet, hasProtagonistFocus, Lumpy Space Princess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtagonistFocus Context triple: [Be Sweet, hasProtagonistFocus, Lumpy Space Princess]
-
A.
hasProtagonist
chosen
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
B.
hasMainProtagonistTrait
Indicates that the specified trait is a defining or primary characteristic of the main protagonist.
-
C.
usesFirstPersonNarrator
Indicates that a narrative work is told from the perspective of an "I" character who is part of the story.
-
D.
hasSpyProtagonist
Indicates that the main character in the work is a spy or primarily engaged in espionage activities.
-
E.
hasSpiritProtagonist
Indicates that the primary or central character in a narrative is a spirit or non-corporeal being.
- F. None of above.
Provenance (4 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0357f9670081908a7ba1cd46a0b46a |
completed | May 12, 2026, 4:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38682e25348190bed03618371f6dd9 |
completed | June 21, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_6a03575e3258819093303248d1569f95 |
completed | May 12, 2026, 4:37 p.m. |
Created at: May 3, 2026, 4:01 p.m.