Triple
T36938090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gill Grunt |
E913670
|
entity |
| Predicate | hasFigureVariants |
P186756
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Gill Grunt, hasFigureVariants, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFigureVariants Context triple: [Gill Grunt, hasFigureVariants, yes]
-
A.
hasVariantDepiction
Indicates that one entity is depicted in an alternative or modified visual form relative to another depiction of the same subject.
-
B.
hasVariantsIn
Indicates that an entity exists in multiple alternative forms or versions within a specified context or set.
-
C.
hasVariantSeries
Indicates a relationship where one entity is a variant or alternative series derived from or associated with another series.
-
D.
toyFigureVariantOf
chosen
Indicates that one toy figure is a variant or alternate version of another toy figure, typically differing in features such as color, accessories, or minor design details while representing the same underlying character or model.
-
E.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of 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_69f76e8a6a5c81909c1febf32bf3fe23 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00383e868c819098fd17e25fcbdb04 |
completed | May 10, 2026, 7:48 a.m. |
| PD | Predicate disambiguation | batch_6a0037cc59688190b7b9da939a413db3 |
completed | May 10, 2026, 7:46 a.m. |
Created at: May 3, 2026, 4:13 p.m.