Triple
T17685672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gyaos |
E440880
|
entity |
| Predicate | groupVariant |
P72811
|
FINISHED |
| Object | swarm of Gyaos in Heisei trilogy |
—
|
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: swarm of Gyaos in Heisei trilogy | Statement: [Gyaos, groupVariant, swarm of Gyaos in Heisei trilogy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groupVariant Context triple: [Gyaos, groupVariant, swarm of Gyaos in Heisei trilogy]
-
A.
hasVariantGroup
chosen
Indicates that an entity is associated with a specific group of related variants that share common characteristics or classification.
-
B.
productVariant
Indicates that one entity is a specific variant or version of a more general product entity.
-
C.
governsVariant
Indicates a regulatory relationship where one entity controls, influences, or determines the behavior or state of a specific variant of another entity.
-
D.
rulesVariantOf
Indicates that one set of rules is a modified or alternative version derived from another set of rules.
-
E.
exportVariantOf
Indicates that one entity is an exported version or externally released form derived from another, original 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47047d90c8190a172201f3de6db87 |
completed | April 19, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:02 a.m.