Triple
T1964014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khan Noonien Singh |
E42647
|
entity |
| Predicate | geneticStatus |
P34447
|
FINISHED |
| Object | genetically engineered |
—
|
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 | Statement: [Khan Noonien Singh, geneticStatus, genetically engineered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geneticStatus Context triple: [Khan Noonien Singh, geneticStatus, genetically engineered]
-
A.
geneticInfluence
Indicates that one entity affects or contributes to the genetic traits, characteristics, or heredity of another entity.
-
B.
geneticAffinity
Indicates a relationship where entities share a notable degree of genetic similarity or relatedness.
-
C.
requiresGeneticConsideration
Indicates that the subject involves or depends on genetic factors that must be taken into account in decision-making, analysis, or management.
-
D.
geneticRelation
Indicates that two entities are connected through a hereditary or familial genetic relationship.
-
E.
guthrieClassification
Indicates a categorization relationship where an entity is assigned a class or type according to the Guthrie classification system.
- 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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb68a8e608190bc37a85913b3cd44 |
completed | March 7, 2026, 5:24 a.m. |
| PD | Predicate disambiguation | batch_69abaff5dbd48190a9d36ca60de151db |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb6893eb881908923f0168374596a |
completed | March 7, 2026, 5:24 a.m. |
Created at: March 4, 2026, 7:36 p.m.