Triple
T18784205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bithorax complex |
E459331
|
entity |
| Predicate | hasSequenceFeature |
P68686
|
FINISHED |
| Object | homeobox domains in encoded proteins |
—
|
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: homeobox domains in encoded proteins | Statement: [bithorax complex, hasSequenceFeature, homeobox domains in encoded proteins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSequenceFeature Context triple: [bithorax complex, hasSequenceFeature, homeobox domains in encoded proteins]
-
A.
hasProteinFeature
chosen
Indicates that a protein possesses a specific structural or functional feature, such as a domain, motif, or modification site.
-
B.
hasFeatureID
Indicates that an entity is associated with a specific feature identified by a unique ID.
-
C.
hasTypicalSequence
Indicates that there is a usual or commonly occurring order or progression in which the related entities or events take place.
-
D.
featuresSequence
Indicates that one entity presents or contains another entity as an ordered sequence of features or elements.
-
E.
isFeatureLength
Indicates that something (typically a film or video) has a duration long enough to be considered a full-length, standard feature.
- 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.