Triple
T17685653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gyaos |
E440880
|
entity |
| Predicate | originInHeiseiSeries |
P128573
|
FINISHED |
| Object | genetically engineered bio-weapon |
—
|
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: genetically engineered bio-weapon | Statement: [Gyaos, originInHeiseiSeries, genetically engineered bio-weapon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originInHeiseiSeries Context triple: [Gyaos, originInHeiseiSeries, genetically engineered bio-weapon]
-
A.
eraStartHeiseiYear
Indicates the calendar year in which the Heisei era begins for a given context or system of dating.
-
B.
eraNumberInJapan
Indicates the specific numbered position of a historical era within the sequence of Japanese eras.
-
C.
dateOfIntroductionToJapan
Indicates the date on which something was first introduced or brought into Japan.
-
D.
TaishoNumber
Indicates that an entity is associated with a specific Taisho catalog or numbering system identifier.
-
E.
seriesOrigin
Indicates that one entity is the original source or starting point from which a series or sequence of related entities is derived.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 10:02 a.m.