Triple
T27867230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ben Edlund |
E704387
|
entity |
| Predicate | hasCreatedFictionalCharacter |
P40162
|
FINISHED |
| Object | The Tick |
—
|
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: The Tick | Statement: [Ben Edlund, hasCreatedFictionalCharacter, The Tick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCreatedFictionalCharacter Context triple: [Ben Edlund, hasCreatedFictionalCharacter, The Tick]
-
A.
coCreatedCharactersWith
Indicates that two or more entities jointly created one or more characters together.
-
B.
creatorOfCharacter
chosen
Indicates that one entity is the originator or author who created or conceived the other entity as a character.
-
C.
fictionalCharacterAssisted
Indicates that one fictional character provided help, support, or assistance to another fictional character.
-
D.
hasFictionalWork
Indicates that one entity is the creator, owner, or source of a fictional work associated with another entity.
-
E.
composedByFictionalCharacter
Indicates that a work or piece of content is (within the narrative) created or authored by a fictional character.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 6:21 p.m.