Triple
T28897904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mortus |
E732877
|
entity |
| Predicate | creatorRoleInFiction |
P19360
|
FINISHED |
| Object | comic-book creator |
—
|
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-book creator | Statement: [Mortus, creatorRoleInFiction, comic-book creator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creatorRoleInFiction Context triple: [Mortus, creatorRoleInFiction, comic-book creator]
-
A.
creatorOfCharacter
Indicates that one entity is the originator or author who created or conceived the other entity as a character.
-
B.
creatorInStory
Indicates that one entity is the creator (e.g., author, originator, or maker) of another entity within the context of a specific story or narrative.
-
C.
creativeRole
chosen
Indicates that an entity holds a specific creative function or responsibility in relation to another entity, such as a work or project.
-
D.
producerInFiction
Indicates that an entity serves as a producer (e.g., of a show, film, or other work) within a fictional context or narrative.
-
E.
literaryRole
Indicates the specific narrative or functional role an entity holds within a literary work or text.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: April 28, 2026, 8 a.m.