Triple
T19245328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INS gene |
E481234
|
entity |
| Predicate | hasStrandOrientation |
P42088
|
FINISHED |
| Object | plus strand |
—
|
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: plus strand | Statement: [INS gene, hasStrandOrientation, plus strand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStrandOrientation Context triple: [INS gene, hasStrandOrientation, plus strand]
-
A.
hasStrand
chosen
Indicates that one entity possesses or is associated with a particular strand or orientation relative to another entity.
-
B.
hasStripeOrientation
Indicates the directional arrangement or alignment of stripes present on an entity.
-
C.
originalChannelStrand
Indicates that one entity is the original strand or source channel from which another channel or strand is derived or referenced.
-
D.
hasOrientation
Indicates that one entity is positioned or directed in a specific spatial or conceptual alignment relative to a reference frame or another entity.
-
E.
hasRegionalOrientation
Indicates that an entity is oriented toward, focused on, or primarily associated with a specific geographic region.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb2c34e88190a338e5a7ba906425 |
completed | April 20, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:27 p.m.