Triple
T29057517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevin Hopgood |
E735428
|
entity |
| Predicate | hasCreatedCharacterFor |
P176002
|
FINISHED |
| Object | Marvel Comics |
—
|
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: Marvel Comics | Statement: [Kevin Hopgood, hasCreatedCharacterFor, Marvel Comics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCreatedCharacterFor Context triple: [Kevin Hopgood, hasCreatedCharacterFor, Marvel Comics]
-
A.
hasPrimaryCharacter
Indicates that an entity features another entity as its main or central character.
-
B.
createdByCharacterRole
Indicates that something (such as a work, item, or event) was brought into existence or produced by an entity acting in a specific character role.
-
C.
currentCharacter
Indicates that an entity is the character presently in focus or being actively considered in a given context or sequence.
-
D.
hasFounderCharacter
Indicates that an entity has a founder who possesses a specified character trait or set of personal qualities.
-
E.
characterSelection
Indicates the relationship where a user or system chooses one or more characters from a set of available options.
- F. None of above. chosen
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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6db3606808190a80c6e9f5da5b33e |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db1bc348819097c844f76e2fa4fe |
completed | May 3, 2026, 5:20 a.m. |
Created at: April 28, 2026, 10:12 a.m.