Triple
T31351678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feast |
E799608
|
entity |
| Predicate | starsCharacterPersona |
P155206
|
FINISHED |
| Object | World Champion persona |
—
|
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: World Champion persona | Statement: [Feast, starsCharacterPersona, World Champion persona]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: starsCharacterPersona Context triple: [Feast, starsCharacterPersona, World Champion persona]
-
A.
characterPersona
chosen
Indicates that one entity embodies, represents, or assumes the persona, role, or character identity specified by another entity.
-
B.
stagePersonaOf
Indicates a relationship where one entity is the staged or performed persona, role, or character representation of another entity.
-
C.
storyCharacterizedAs
Indicates that a story is described, portrayed, or defined as having a particular quality, style, or attribute.
-
D.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
E.
styleCharacter
Indicates that one entity defines, influences, or characterizes the stylistic qualities or manner of expression of another entity.
- 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:17 p.m.