Triple
T35198760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "It's clobberin' time!" |
E1016338
|
entity |
| Predicate | characterAliasContext |
P41555
|
FINISHED |
| Object | Ben Grimm is also known as the Thing |
—
|
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: Ben Grimm is also known as the Thing | Statement: ["It's clobberin' time!", characterAliasContext, Ben Grimm is also known as the Thing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterAliasContext Context triple: ["It's clobberin' time!", characterAliasContext, Ben Grimm is also known as the Thing]
-
A.
characterAlias
chosen
Indicates that one character is known or referred to by an alternative name or alias.
-
B.
associatedWithCharacterAlias
Indicates that one entity is linked to or connected with an alternative name or alias used for a particular character.
-
C.
characterName
Indicates that an entity has a specific name used to identify its character.
-
D.
characterReveals
Indicates that one character discloses or makes known information, feelings, or intentions to another character.
-
E.
characterPersona
Indicates that one entity embodies, represents, or assumes the persona, role, or character identity specified by another entity.
- 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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff90b673248190b4dda9e005642d17 |
completed | May 9, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69ff8d5bee1081909274052945e98a6f |
completed | May 9, 2026, 7:39 p.m. |
Created at: May 3, 2026, 4:02 p.m.