Triple
T18784248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antennapedia complex |
E459332
|
entity |
| Predicate | geneticLocusType |
P68690
|
FINISHED |
| Object | complex locus |
—
|
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: complex locus | Statement: [Antennapedia complex, geneticLocusType, complex locus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geneticLocusType Context triple: [Antennapedia complex, geneticLocusType, complex locus]
-
A.
hasGeneticLocus
Indicates that a genetic feature or trait is located at, or associated with, a specific position (locus) on a genome or chromosome.
-
B.
geneType
Indicates the specific category or classification of a gene based on its functional or structural characteristics.
-
C.
geneticElement
Indicates that one entity is a genetic element (such as a gene, sequence, or structural unit of genetic material) associated with or characterized by the other entity.
-
D.
locusDescription
Indicates how the spatial position or location of an entity is described or characterized.
-
E.
chromosomalLocation
chosen
Indicates the specific position or region on a chromosome where a genetic element (such as a gene or marker) is located.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5977ffa648190be5f682bba47fb0a |
completed | April 20, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.