Triple
T3760391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miracle Max |
E82145
|
entity |
| Predicate | comicRole |
P23263
|
FINISHED |
| Object | comic relief character |
—
|
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: comic relief character | Statement: [Miracle Max, comicRole, comic relief character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comicRole Context triple: [Miracle Max, comicRole, comic relief character]
-
A.
supportingCharacter
Indicates that one entity plays a secondary or assisting role in the story or context relative to another primary entity.
-
B.
fictionalCharacter
Indicates that one entity is a fictional character that appears within the narrative world of another entity (such as a work, series, or franchise).
-
C.
featuresCharacterRole
chosen
Indicates that a work includes a character appearing in a specific narrative or functional role.
-
D.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
E.
fictionalCharacterFrom
Indicates that a fictional character originates from, or is created within, a particular work, universe, or source.
- 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_69ad8b1db40081908b61ffa6b78afd4d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcbc3d3f48190974cec104080949f |
completed | March 8, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69adc04c851c8190ae5eaebf36df539b |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.