Triple
T12685788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hank McCoy |
E303061
|
entity |
| Predicate | hasAlteredForm |
P18099
|
FINISHED |
| Object | feline-like blue-furred form |
—
|
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: feline-like blue-furred form | Statement: [Hank McCoy, hasAlteredForm, feline-like blue-furred form]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlteredForm Context triple: [Hank McCoy, hasAlteredForm, feline-like blue-furred form]
-
A.
hasReformedForm
Indicates that an entity has a later, modified, or updated form that results from a process of reform or restructuring.
-
B.
alternativeForm
chosen
Indicates that one entity is an alternative version, variant, or representation of another entity.
-
C.
hasAlterationPeriod
Indicates that an entity is associated with a specific time span during which changes, modifications, or alterations may occur or are valid.
-
D.
hasNonStandardForm
Indicates that an entity possesses a form, variant, or representation that deviates from the standard, canonical, or commonly accepted form.
-
E.
hasHumanModification
Indicates that an entity has been altered, influenced, or modified as a result of human activity or intervention.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961d7cd4c81909521839ef5859799 |
completed | April 10, 2026, 8:47 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:21 p.m.