Triple
T28462590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neil Munro |
E720195
|
entity |
| Predicate | createdFictionalCharacter |
P40162
|
FINISHED |
| Object | Para Handy |
—
|
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: Para Handy | Statement: [Neil Munro, createdFictionalCharacter, Para Handy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdFictionalCharacter Context triple: [Neil Munro, createdFictionalCharacter, Para Handy]
-
A.
fictionalCharacterAssisted
Indicates that one fictional character provided help, support, or assistance to another fictional character.
-
B.
fictionalCharacterFrom
Indicates that a fictional character originates from, or is created within, a particular work, universe, or source.
-
C.
fictionalPersonaOf
Indicates that one entity is a fictional or narrative persona, alter ego, or character representation of another (typically real or primary) entity.
-
D.
creatorOfCharacter
chosen
Indicates that one entity is the originator or author who created or conceived the other entity as a character.
-
E.
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).
- 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: April 28, 2026, 2:41 a.m.